...

These new Route Tables will be created prior to the migration, but will not actually be utilized until the migration is executed. When migration is executed, subnets associated with the v1 Route Tables will be re-associated to the corresponding v2 Route Tables. Similarly, if the "main" Route Table for the VPC references a VGW, the corresponding v2 Route Table will be set as the "main" Route Table.

Transit Gateway Attachments

...

For this migration, we are tagging AWS resources to provide information about how the each resource is involved in the migration, the v1 architecture, and the v2 architecture.

Tag Key	Tag Values	Description	VPC	Subnets	Route Tables	Transit Gateway Attachments	Virtual Private Gateways	Direct Connect Virtual Interfaces
cit:dc-arch-migration-target	yes/no	Will this resource itself be affected as part of the migration?
cit:dc-arch-migration-description	prose	Description of planned changes to this resource
cit:dc-arch-version	v1/v2	Is this a v1 or v2 architecture resource? After migration, v1 resources utilized in the v2 architecture will be relabeled as v2 resources.
cit:dc-arch-migration-new-resource	yes/no	Is this a new resource specifically created for the v2 architecture?	n/a	n/a			n/a	n/a
cit:dc-arch-migration-replaces	resource ID	If this v2 resource will be replacing a v1 resource, this ID references the resource that will be replaced.	n/a	n/a		n/a	n/a	n/a

Resource Deletion

After migration is complete, a very few number of resources will be deleted. These are:

• Virtual Private Gateways (VGWs)
• Direct Connect Virtual Private Interfaces (DCVIFs)

Neither VGWs nor DCVIFs have a role in the v2 architecture.

v1 Route Tables will not be deleted, but will not be used in the v2 architecture. Cornell AWS account owners can delete the v1 Route Tables if they wish. Once the VGWs are deleted, those v1 Route Tables will not be all that functional.

Timeline

References