- HTTP request
- Path parameters
- Request body
- Response body
- Authorization scopes
- IAM Permissions
- Try it!
Returns the specified interconnect attachment.
HTTP request
GET https://compute.googleapis.com/compute/v1/projects/{project}/regions/{region}/interconnectAttachments/{interconnectAttachment}
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
project |
Project ID for this request. |
region |
Name of the region for this request. |
interconnect |
Name of the interconnect attachment to return. |
Request body
The request body must be empty.
Response body
Represents an Interconnect Attachment (VLAN) resource.
You can use Interconnect attachments (VLANS) to connect your Virtual Private Cloud networks to your on-premises networks through an Interconnect. For more information, read Creating VLAN Attachments.
If successful, the response body contains data with the following structure:
JSON representation |
---|
{ "kind": string, "description": string, "selfLink": string, "id": string, "creationTimestamp": string, "name": string, "interconnect": string, "router": string, "region": string, "googleReferenceId": string, "mtu": integer, "privateInterconnectInfo": { "tag8021q": integer }, "operationalStatus": enum, "cloudRouterIpAddress": string, "customerRouterIpAddress": string, "type": enum, "pairingKey": string, "adminEnabled": boolean, "vlanTag8021q": integer, "edgeAvailabilityDomain": enum, "candidateSubnets": [ string ], "bandwidth": enum, "partnerMetadata": { "partnerName": string, "interconnectName": string, "portalUrl": string }, "labels": { string: string, ... }, "labelFingerprint": string, "state": enum, "partnerAsn": string, "encryption": enum, "ipsecInternalAddresses": [ string ], "dataplaneVersion": integer, "satisfiesPzs": boolean, "stackType": enum, "cloudRouterIpv6Address": string, "customerRouterIpv6Address": string, "candidateIpv6Subnets": [ string ], "cloudRouterIpv6InterfaceId": string, "customerRouterIpv6InterfaceId": string, "subnetLength": integer, "remoteService": string, "configurationConstraints": { "bgpMd5": enum, "bgpPeerAsnRanges": [ { "min": integer, "max": integer } ] } } |
Fields | |
---|---|
kind |
[Output Only] Type of the resource. Always |
description |
An optional description of this resource. |
self |
[Output Only] Server-defined URL for the resource. |
id |
[Output Only] The unique identifier for the resource. This identifier is defined by the server. |
creation |
[Output Only] Creation timestamp in RFC3339 text format. |
name |
Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression |
interconnect |
URL of the underlying Interconnect object that this attachment's traffic will traverse through. |
router |
URL of the Cloud Router to be used for dynamic routing. This router must be in the same region as this InterconnectAttachment. The InterconnectAttachment will automatically connect the Interconnect to the network & region within which the Cloud Router is configured. |
region |
[Output Only] URL of the region where the regional interconnect attachment resides. You must specify this field as part of the HTTP request URL. It is not settable as a field in the request body. |
googleReferenceId |
[Output Only] Google reference ID, to be used when raising support tickets with Google or otherwise to debug backend connectivity issues. [Deprecated] This field is not used. |
mtu |
Maximum Transmission Unit (MTU), in bytes, of packets passing through this interconnect attachment. Only 1440 and 1500 are allowed. If not specified, the value will default to 1440. |
private |
[Output Only] Information specific to an InterconnectAttachment. This property is populated if the interconnect that this is attached to is of type DEDICATED. |
private |
[Output Only] 802.1q encapsulation tag to be used for traffic between Google and the customer, going to and from this network and region. |
operational |
[Output Only] The current status of whether or not this interconnect attachment is functional, which can take one of the following values:
|
cloud |
[Output Only] IPv4 address + prefix length to be configured on Cloud Router Interface for this interconnect attachment. |
customer |
[Output Only] IPv4 address + prefix length to be configured on the customer router subinterface for this interconnect attachment. |
type |
The type of interconnect attachment this is, which can take one of the following values:
|
pairing |
[Output only for type PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of a PARTNER attachment used to initiate provisioning with a selected partner. Of the form "XXXXX/region/domain" |
admin |
Determines whether this Attachment will carry packets. Not present for PARTNER_PROVIDER. |
vlan |
The IEEE 802.1Q VLAN tag for this attachment, in the range 2-4093. Only specified at creation time. |
edge |
Desired availability domain for the attachment. Only available for type PARTNER, at creation time, and can take one of the following values:
|
candidate |
Up to 16 candidate prefixes that can be used to restrict the allocation of cloudRouterIpAddress and customerRouterIpAddress for this attachment. All prefixes must be within link-local address space (169.254.0.0/16) and must be /29 or shorter (/28, /27, etc). Google will attempt to select an unused /29 from the supplied candidate prefix(es). The request will fail if all possible /29s are in use on Google's edge. If not supplied, Google will randomly select an unused /29 from all of link-local space. |
bandwidth |
Provisioned bandwidth capacity for the interconnect attachment. For attachments of type DEDICATED, the user can set the bandwidth. For attachments of type PARTNER, the Google Partner that is operating the interconnect must set the bandwidth. Output only for PARTNER type, mutable for PARTNER_PROVIDER and DEDICATED, and can take one of the following values:
|
partner |
Informational metadata about Partner attachments from Partners to display to customers. Output only for PARTNER type, mutable for PARTNER_PROVIDER, not available for DEDICATED. |
partner |
Plain text name of the Partner providing this attachment. This value may be validated to match approved Partner values. |
partner |
Plain text name of the Interconnect this attachment is connected to, as displayed in the Partner's portal. For instance "Chicago 1". This value may be validated to match approved Partner values. |
partner |
URL of the Partner's portal for this Attachment. Partners may customise this to be a deep link to the specific resource on the Partner portal. This value may be validated to match approved Partner values. |
labels |
Labels for this resource. These can only be added or modified by the |
label |
A fingerprint for the labels being applied to this InterconnectAttachment, which is essentially a hash of the labels set used for optimistic locking. The fingerprint is initially generated by Compute Engine and changes after every request to modify or update labels. You must always provide an up-to-date fingerprint hash in order to update or change labels, otherwise the request will fail with error To see the latest fingerprint, make a A base64-encoded string. |
state |
[Output Only] The current state of this attachment's functionality. Enum values ACTIVE and UNPROVISIONED are shared by DEDICATED/PRIVATE, PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER_REQUEST_RECEIVED, and PENDING_CUSTOMER are used for only PARTNER and PARTNER_PROVIDER interconnect attachments. This state can take one of the following values:
|
partner |
Optional BGP ASN for the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Output only for PARTNER type, input only for PARTNER_PROVIDER, not available for DEDICATED. |
encryption |
Indicates the user-supplied encryption option of this VLAN attachment (interconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED attachments. Possible values are:
|
ipsec |
A list of URLs of addresses that have been reserved for the VLAN attachment. Used only for the VLAN attachment that has the encryption option as IPSEC. The addresses must be regional internal IP address ranges. When creating an HA VPN gateway over the VLAN attachment, if the attachment is configured to use a regional internal IP address, then the VPN gateway's IP address is allocated from the IP address range specified here. For example, if the HA VPN gateway's interface 0 is paired to this VLAN attachment, then a regional internal IP address for the VPN gateway interface 0 will be allocated from the IP address specified for this VLAN attachment. If this field is not specified when creating the VLAN attachment, then later on when creating an HA VPN gateway on this VLAN attachment, the HA VPN gateway's IP address is allocated from the regional external IP address pool. |
dataplane |
[Output Only] Dataplane version for this InterconnectAttachment. This field is only present for Dataplane version 2 and higher. Absence of this field in the API output indicates that the Dataplane is version 1. |
satisfies |
[Output Only] Reserved for future use. |
stack |
The stack type for this interconnect attachment to identify whether the IPv6 feature is enabled or not. If not specified, This field can be both set at interconnect attachments creation and update interconnect attachment operations. |
cloud |
[Output Only] IPv6 address + prefix length to be configured on Cloud Router Interface for this interconnect attachment. |
customer |
[Output Only] IPv6 address + prefix length to be configured on the customer router subinterface for this interconnect attachment. |
candidate |
This field is not available. |
cloud |
This field is not available. |
customer |
This field is not available. |
subnet |
Length of the IPv4 subnet mask. Allowed values:
The default value is 29, except for Cross-Cloud Interconnect connections that use an InterconnectRemoteLocation with a constraints.subnetLengthRange.min equal to 30. For example, connections that use an Azure remote location fall into this category. In these cases, the default value is 30, and requesting 29 returns an error. Where both 29 and 30 are allowed, 29 is preferred, because it gives Google Cloud Support more debugging visibility. |
remote |
[Output Only] If the attachment is on a Cross-Cloud Interconnect connection, this field contains the interconnect's remote location service provider. Example values: "Amazon Web Services" "Microsoft Azure". The field is set only for attachments on Cross-Cloud Interconnect connections. Its value is copied from the InterconnectRemoteLocation remoteService field. |
configuration |
[Output Only] Constraints for this attachment, if any. The attachment does not work if these constraints are not met. |
configuration |
[Output Only] Whether the attachment's BGP session requires/allows/disallows BGP MD5 authentication. This can take one of the following values: MD5_OPTIONAL, MD5_REQUIRED, MD5_UNSUPPORTED. For example, a Cross-Cloud Interconnect connection to a remote cloud provider that requires BGP MD5 authentication has the interconnectRemoteLocation attachmentConfigurationConstraints.bgp_md5 field set to MD5_REQUIRED, and that property is propagated to the attachment. Similarly, if BGP MD5 is MD5_UNSUPPORTED, an error is returned if MD5 is requested. |
configuration |
[Output Only] interconnectAttachments.list of ASN ranges that the remote location is known to support. Formatted as an array of inclusive ranges {min: min-value, max: max-value}. For example, [{min: 123, max: 123}, {min: 64512, max: 65534}] allows the peer ASN to be 123 or anything in the range 64512-65534. This field is only advisory. Although the API accepts other ranges, these are the ranges that we recommend. |
configuration |
|
configuration |
|
Authorization scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/compute.readonly
https://www.googleapis.com/auth/compute
https://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.
IAM Permissions
In addition to any permissions specified on the fields above, authorization requires one or more of the following IAM permissions:
compute.interconnectAttachments.get
To find predefined roles that contain those permissions, see Compute Engine IAM Roles.