Transit Gateways
Create Transit Gateway
Creates a new transit gateway attachment for a given network. The attachment type is determined by the transit_gateway_attachment_config.kind field. Supported types: aws-transit-gateway-attachment, aws-vpc-peering-attachment, aws-resource-endpoint-attachment, azure-vnet-peering-attachment, azure-vhub-peering-attachment, and gcp-vpc-peering-attachment. Creation is asynchronous — the transit gateway starts in initializing state and transitions to ready once provisioned.
post/v2/cloud-gateways/networks/{networkId}/transit-gateways
Path parameters
networkIdstring uuid required
The network ID to operate on. For serverless.v1 kind of cloud gateways, this field should be omitted.
Example:36ae63d3-efd1-4bec-b246-62aa5d3f5695
The network to operate on.
Request body
Example request
{
"name": "us-east-2 transit gateway",
"dns_config": [
{
"remote_dns_server_ip_addresses": [
"10.0.0.2"
],
"domain_proxy_list": [
"foobar.com"
]
}
],
"cidr_blocks": [
"10.0.0.0/8",
"100.64.0.0/10",
"172.16.0.0/12"
]
}Response
Response format for creating a transit gateway.
Example response
{
"name": "us-east-2 transit gateway",
"dns_config": [
{
"remote_dns_server_ip_addresses": [
"10.0.0.2"
],
"domain_proxy_list": [
"foobar.com"
]
}
],
"cidr_blocks": [
"10.0.0.0/8",
"100.64.0.0/10",
"172.16.0.0/12"
],
"id": "0850820b-d153-4a2a-b9be-7d2204779139",
"state_metadata": {
"reported_status": "ERROR",
"reason": "Transit Gateway Attachment configuration could not find a resource with the provided ram share arn.\n"
},
"entity_version": 1,
"created_at": "2022-11-04T20:10:06.927Z",
"updated_at": "2022-11-04T20:10:06.927Z"
}