- Newest
- Most votes
- Most comments
Currently, the methods for provisioning Direct Connect are: AWS CLI, SDK/API, or Management Console; Direct Connect does not currently have support for CloudFormation.
Here is the API Reference : CreateDirectConnectGateway
For background, Direct Connect links customer internal networks to an Direct Connect location over a standard Ethernet fiber-optic cable. One end of the cable is connected to your router, the other to an Direct Connect router. With this connection in place, you can create virtual interfaces directly to the Amazon Web Services Cloud (for example, to Amazon EC2 and Amazon S3) and to Amazon VPC, bypassing Internet service providers in your network path. A connection provides access to all Amazon Web Services Regions except the China (Beijing) and (China) Ningxia Regions. Amazon Web Services resources in the China Regions can only be accessed through locations associated with those Regions.
Use the AWS CLI, SDK/API, or the Web Console to create or modify a Direct Connect gateway and to allocate and associate virtual interfaces (the equivalent to VLANs).
To manage your infrastructure as code, you will need to use scripts and/or code via a programming language such as Java.
As of now, Direct Connect Gateway is not supported in AWS CloudFormation. The GitHub issue - AWS::DirectConnect::* support #876 referenced outlines that limitation.
For creating a Direct Connect Gateway, you would need to use the AWS Management Console, AWS CLI, or SDKs instead of CloudFormation. If you're looking to automate your infrastructure, consider combining CloudFormation for other resources and using a script or Lambda function for the Direct Connect Gateway.
Relevant content
asked 2 years ago
asked 2 years ago
asked 6 years ago
- AWS OFFICIALUpdated 3 years ago
