gcloud compute interconnects attachments dedicated create

NAME
gcloud compute interconnects attachments dedicated create - create a Compute Engine dedicated interconnect attachment
SYNOPSIS
gcloud compute interconnects attachments dedicated createNAME--interconnect=INTERCONNECT--router=ROUTER[--bandwidth=BANDWIDTH][--candidate-cloud-router-ip-address=CANDIDATE_CLOUD_ROUTER_IP_ADDRESS][--candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS][--candidate-customer-router-ip-address=CANDIDATE_CUSTOMER_ROUTER_IP_ADDRESS][--candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS][--candidate-ipv6-subnets=[IPV6_SUBNET,…]][--candidate-subnets=[SUBNET,…]][--cloud-router-ipv6-interface-id=INTERFACE_ID][--customer-router-ipv6-interface-id=PEER_INTERFACE_ID][--description=DESCRIPTION][--enable-admin][--encryption=ENCRYPTION][--ipsec-internal-addresses=[ADDRESSES]][--mtu=MTU][--region=REGION][--resource-manager-tags=[KEY=VALUE,…]][--stack-type=STACK_TYPE][--subnet-length=SUBNET_LENGTH][--vlan=VLAN][GCLOUD_WIDE_FLAG]
DESCRIPTION
gcloud compute interconnects attachments dedicated create is usedto create a dedicated interconnect attachments. An interconnect attachment iswhat binds the underlying connectivity of an interconnect to a path into and outof the customer's cloud network.
POSITIONAL ARGUMENTS
NAME
Name of the interconnect attachment to create.
REQUIRED FLAGS
--interconnect=INTERCONNECT
The interconnect for the interconnect attachment
--router=ROUTER
Google Cloud Router to use for dynamic routing.
OPTIONAL FLAGS
--bandwidth=BANDWIDTH
Provisioned capacity of the attachment.BANDWIDTH mustbe one of:
50m
50 Mbit/s
100m
100 Mbit/s
200m
200 Mbit/s
300m
300 Mbit/s
400m
400 Mbit/s
500m
500 Mbit/s
1g
1 Gbit/s
2g
2 Gbit/s
5g
5 Gbit/s
10g
10 Gbit/s
20g
20 Gbit/s
50g
50 Gbit/s
100g
100 Gbit/s
400g
400 Gbit/s
--candidate-cloud-router-ip-address=CANDIDATE_CLOUD_ROUTER_IP_ADDRESS
Single IPv4 address + prefix length to be configured on the cloud routerinterface for this interconnect attachment. Example: 203.0.113.1/29
--candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS
Single IPv6 address + prefix length to be configured on the cloud routerinterface for this interconnect attachment. Example: 2001:db8::1/125
--candidate-customer-router-ip-address=CANDIDATE_CUSTOMER_ROUTER_IP_ADDRESS
Single IPv4 address + prefix length to be configured on the customer routerinterface for this interconnect attachment. Example: 203.0.113.2/29
--candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS
Single IPv6 address + prefix length to be configured on the customer routerinterface for this interconnect attachment. Example: 2001:db8::2/125
--candidate-ipv6-subnets=[IPV6_SUBNET,…]
Thecandididate-ipv6-subnets field is not available.
--candidate-subnets=[SUBNET,…]
Up to 16 candidate prefixes that can be used to restrict the allocation ofcloudRouterIpAddress andcustomerRouterIpAddress forthis attachment. All prefixes must be within link-local address space. Googleattempts to select an unused subnet of SUBNET_LENGTH from the supplied candidatesubnet(s), or all of link-local space if no subnets supplied. Google does notre-use a subnet already in-use by your project, even if it's contained in one ofthe candidate subnets. The request fails if all candidate subnets are in use atGoogle's edge.
--cloud-router-ipv6-interface-id=INTERFACE_ID
cloud-router-ipv6-interface-id field is not available.
--customer-router-ipv6-interface-id=PEER_INTERFACE_ID
customer-router-ipv6-interface-id field is not available.
--description=DESCRIPTION
Human-readable plain-text description of attachment.
--enable-admin
Administrative status of the interconnect attachment. If not provided oncreation, defaults to enabled. When this is enabled, the attachment isoperational and will carry traffic. Use --no-enable-admin to disable it.
--encryption=ENCRYPTION
Indicates the user-supplied encryption option for this interconnect attachment(VLAN attachment).

Possible values are:

NONE - This is the default value, which means the interconnectattachment carries unencrypted traffic. VMs can send traffic to or receivetraffic from such interconnect attachment.

IPSEC - The interconnect attachment carries only traffic that isencrypted by an IPsec device; for example, an HA VPN gateway or third-partyIPsec VPN. VMs cannot directly send traffic to or receive traffic from such aninterconnect attachment. To use HA VPN over Cloud Interconnect, the interconnectattachment must be created with this option.

ENCRYPTION must be one of:IPSEC,NONE.

--ipsec-internal-addresses=[ADDRESSES]
List of IP address range names that have been reserved for the interconnectattachment (VLAN attachment). Use this option only for an interconnectattachment that has its encryption option set as IPSEC. Currently only oneinternal IP address range can be specified for each attachment. When creating anHA VPN gateway for the interconnect attachment, if the attachment is configuredto use a regional internal IP address, then the VPN gateway's IP address isallocated from the IP address range specified here. If this field is notspecified when creating the interconnect attachment, then when creating any HAVPN gateways for this interconnect attachment, the HA VPN gateway's IP addressis allocated from a regional external IP address pool.
--mtu=MTU
Maximum transmission unit (MTU) is the size of the largest IP packet passingthrough this interconnect attachment. Must be one of 1440, 1460, 1500, or 8896.If not specified, the value will default to 1440.
--region=REGION
Region of the interconnect attachment to create. If not specified, you might beprompted to select a region (interactive mode only).

To avoid prompting when this flag is omitted, you can set thecompute/region property:

gcloudconfigsetcompute/regionREGION

A list of regions can be fetched by running:

gcloudcomputeregionslist

To unset the property, run:

gcloudconfigunsetcompute/region

Alternatively, the region can be stored in the environment variableCLOUDSDK_COMPUTE_REGION.

--resource-manager-tags=[KEY=VALUE,…]
A comma-separated list of Resource Manager tags to apply to the interconnect.
--stack-type=STACK_TYPE
Stack type of the protocol(s) enabled on this interconnect attachment.STACK_TYPE must be one of:
IPV4_IPV6
Both IPv4 and IPv6 protocols are enabled on this attachment.
IPV4_ONLY
Only IPv4 protocol is enabled on this attachment.
--subnet-length=SUBNET_LENGTH
Length of the IPv4 subnet mask for this attachment. 29 is the default value,except for attachments on Cross-Cloud Interconnects whose remote location's"constraints.subnetLengthRange" field specifies a minimum subnet length of 30.In that case, the default value is 30. The default value is recommended whenthere's no requirement on the subnet length.SUBNET_LENGTH must be one of:29,30.
--vlan=VLAN
Desired VLAN for this attachment, in the range 2-4093. If not supplied, Googlewill automatically select a VLAN.
GCLOUD WIDE FLAGS
These flags are available to all commands:--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.

Run$gcloud help for details.

NOTES
These variants are also available:
gcloudalphacomputeinterconnectsattachmentsdedicatedcreate
gcloudbetacomputeinterconnectsattachmentsdedicatedcreate

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-01-27 UTC.