...

Phase	Stage	Timeframe	Status	Activity	Impact on Cornell AWS Account VPC Networks
Preparation	Data Collection	November 2022		Gather information about Direct Connect resources and connected VPCs in Cornell AWS accounts	none
	Resource Tagging	14 Dec 2022		Add tags to existing resources in customer accounts to assist with targeting, identification, status, intended disposition	none
	Resource Groups			Create Transit Gateway in CIT AWS account Create Resource Groups for resources involved in the migration in customer accounts	none
	Customer Input #1	15 Dec 2022 - 02 Jan 2023		Cornell AWS account owner/admin review Cornell AWS account owner/admin feedback solicited	none
Migration	Transit Gateway Attachments	03 Jan 2023 - 06 Jan 2023		Utility Subnets Transit Gateway Attachments created in customer accounts v2 Route Tables created in customer accounts NACLs for Utility Subnets	none
	Customer Input #2	09 Jan 2023 - 13 Jan 2023		Cornell AWS account owner/admin review Cornell AWS account owner/admin feedback solicited Route Table and/or TGW Attachments adjusted according to customer input	none
	VPC Routing Updated	Originally Jan 16, but that is MLK day. So, 17 Jan 2023		v2 Route Tables activated v1 Route Tables deactivated	VPC-to-campus traffic will be routed through the v2 architecture
	Campus Direct Connect Routes Updated	18 Jan 2023		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	23 Jan 2023 - 31 Jan 2023		VGWs and DC VIFs in customer accounts deleted	none
	Campus Direct Connect Cleanup			Campus Direct Connect resources deleted or decommissioned	none

Alternate Migration Days

Customers have the option to request that migration for their VPC(s) occur during the week of Jan 9-13 instead of the default migration dates of January 17 and 18. This is especially encouraged for customers that have a separate sandbox or development VPC that needs to be migrated. We can also support taking both migration steps on the same alternate day, but we'd like to leave a 1-4 hour gap between migration steps to confirm that the "VPC Routing Updated" step was successful before continuing to the "Campus Direct Connect Routes Updates" step.

Rollback

Both the "VPC Routing Updated" and the "Campus Direct Connect Routes Updated" have simple rollback steps. If you discover problems with networking in your VPC after either step and think the change needs to be rolled back, send an email to cloud-incident@cornell.edu and ping Paul Allen (pea1) on Teams.

FAQs

How do I tell if my AWS account will be affected by this change?

...