| Warning |
|---|
This page is being retained for historical purposes, but is no longer maintained. All relevant Direct Connect information about the current (2023 and after) Direct Connect architecture has been migrated to primary customer Direct Connect documentation, Cornell AWS Direct Connect. |
| Table of Contents |
|---|
...
Introduction
...
| Code Block |
|---|
lifecycle {
ignore_changes = [ "tags" ]
} |
Terraform Configuration Templates for Added Resources
| Info |
|---|
This guide does not describe how to import pre-existing resources into Terraform. See Terraform documentation/tutorial for how-to and concepts: Import Terraform Configuration |
Generally, you will take these steps:
- Add the configuration below to your Terraform configuration.
- Edit/customize the added configuration to match reality.
- Import the resources into your Terraform state. (See comments in the .tf files below for specific import commands.)
- Continue to edit/customer the configuration below until a terraform plan doesn't result in Terraform wanting to make any changes.
Utility Subnet Resources
This Terraform configuration will need minor edits to correspond to the resources in your VPC.
| Terraform configuration | utility-resources.tf |
|---|
Route Table Resources
This Terraform configuration is a super basic template of the v2 Route Table resources added to customer VPCs. You will generally want to take one of two approaches:
- Start with the template below and copy/paste/edit to get to a Terraform configuration that matches reality.
- OR - - Copy the pre-existing Terraform configuration for your route tables and add elements from the Terraform template below, to get to a Terraform configuration that matches reality.
| Terraform template | route-tables.tf |
|---|
Other Resources
Transit Gateway Attachment
We recommend that you do not import the Transit Gateway Attachment resource directly into your Terraform configuration. The utility-resources.tf template provides a Terraform data source that you can use in your configuration when you need to reference the TGW ID or the TGW Attachment ID elsewhere in your Terraform.
Secondary VPC CIDR Block
Each customer VPC had secondary a CIDR block added to it. The utility subnets were created from this CIDR. We do not recommend adding a aws_vpc_ipv4_cidr_block_association resource to your Terraform configuration in order to manage this secondary CIDR block into your Terraform configuration. The reason behind this is that these secondary CIDRs were allocated using Amazon VPC IP Address Manager (IPAM) and customers do not have privileges to these IPAM resources.
Virtual Private Gateway
Virtual Private Gateways (VGW) will be detached from VPCs on by CIT. During the week of , VGWs will be deleted entirely. Your Terraform configuration will need to be updated accordingly.
References
- Cornell
- Terraform
- AWS