Phase | Stage | Activity | Impact on Cornell AWS Account VPC Network |
---|
Preparation
| Data Collection | - Gather information about Direct Connect resources and connected VPCs in Cornell AWS accounts
| none |
Resource Tagging | - Add tags to existing resources in customer accounts to assist with targeting, identification, status, intended disposition
| none |
Resource DeploymentGroups | - Create Transit Gateway in CIT AWS account
- Create Resource Groups for resources involved in the migration in customer accounts
| none |
Customer Input #1 | - Customer review and feedback
| none |
Migration
| Transit Gateway Attachments | - Transit Gateway Attachments created in customer accounts
- V2 Route Tables created in customer accounts
| none |
Customer Input #2 | - Cornell AWS account owner review and feedback
- Route Table and/or TGW Attachments adjusted according to customer input
| none |
VPC Routing Updated | - V2 Route Tables activated; V1 Route Tables deactivated
| VPC-to-campus traffic will be routed through the v2 architecture |
Campus Direct Connect Routes Updated | - Campus-side routing updated to begin using the v2 architecture for campus-to-AWS traffic
| campus-to-VPC traffic will be routed through the V2 architecture |
Cleanup | Customer Account Cleanup | - VGWs and DC VIFs in customer accounts deleted
| none |
Campus Direct Connect Cleanup | - Campus Direct Connect resources deleted or decommissioned
| none |