Reference documentation and code samples for the Compute Engine v1 API enum InterconnectAttachment.Types.EdgeAvailabilityDomain.
Desired availability domain for the attachment. Only available for type PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - AVAILABILITY_DOMAIN_1 - AVAILABILITY_DOMAIN_2 For improved reliability, customers should configure a pair of attachments, one per availability domain. The selected availability domain will be provided to the Partner via the pairing key, so that the provisioned circuit will lie in the specified domain. If not specified, the value will default to AVAILABILITY_DOMAIN_ANY.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-08 UTC."],[[["\u003cp\u003eThis page provides reference documentation for the \u003ccode\u003eEdgeAvailabilityDomain\u003c/code\u003e enum within the Google Compute Engine v1 API.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eEdgeAvailabilityDomain\u003c/code\u003e enum is used to specify the desired availability domain for an Interconnect attachment, particularly for type PARTNER.\u003c/p\u003e\n"],["\u003cp\u003eThe available domain options for this enum are \u003ccode\u003eAVAILABILITY_DOMAIN_ANY\u003c/code\u003e, \u003ccode\u003eAVAILABILITY_DOMAIN_1\u003c/code\u003e, \u003ccode\u003eAVAILABILITY_DOMAIN_2\u003c/code\u003e, and \u003ccode\u003eUndefinedEdgeAvailabilityDomain\u003c/code\u003e, with \u003ccode\u003eAVAILABILITY_DOMAIN_ANY\u003c/code\u003e being the default.\u003c/p\u003e\n"],["\u003cp\u003eThis documentation covers a wide range of versions, from the latest 3.6.0 down to 1.0.0, providing a historical overview of its implementation.\u003c/p\u003e\n"],["\u003cp\u003eIt is recommended to setup a pair of attachments, with one per availability domain for increased reliability.\u003c/p\u003e\n"]]],[],null,[]]
