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. |
Info |
---|
Executive Summary
|
...
Tag Key | Tag Values | Description | VPC | Subnets | Route Tables | NACLs ‡ | Transit Gateway | Virtual Private | 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 | n/a | |||
cit:subnet-type | public/private/utility | Is this a private or public subnet? Public subnets are those with a route to an Internet Gateway. Utility subnets will be created specifically to use for TGW Attachments. Private subnets are all subnets that are not public and are not utility subnets. | n/a | n/a | n/a | n/a | n/a | n/a | |||
citcit:tgw-attachment-target | yes/no | Will a Transit Gateway be attached to this subnet? | n/a | n/a | n/a | n/a | n/a | n/a | |||
cit:dc-arch-exclude-tgw-attachment-guidanceroutes | tbdyes/attach/no-attach | This tag provides a place for a human reviewer to provide guidance about whether a TGW attachment should be made to the tagged subnet.
| is applied only to the new Route Table that is created for use by the TGW Attachment utility subnets | n/a | n/a | n/a | n/a | n/a | n/a | ||
cit:dc-vgw | yes/no | Does this Route Table contain rules referencing a VGW? | n/a | n/a | n/a | n/a | n/a | n/a | |||
Cost Center | R524755 | This tag added to TGW Attachments will result in CIT paying for the $0.05/hr cost of attaching a VPC to a TGW. | n/a | n/a | n/a | n/a | n/a | n/a |
‡ Only the NACL created for use by utility subnets will be tagged.
Direct Connect Gateways are also involved in the migration but cannot be tagged.
...
The AWS Transit Gateways used in the v2 architecture require different routing rules than the Virtual Private Gateways (VGW) used in the v1 architecture. Each VPC Route Table that references a Virtual Private Gateway will be duplicated and, in the new Route Table, rules referencing a VGW will be replaced with rules referencing a TGW Attachment. The new Route Tables will not include "blackhole" routes (i.e. routes to resources, like old peering connections, that no longer exist) from the original Route Tables.
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 for the VPC.
...
draw.io source: direct-connect-migration-process.v2.drawio
Anchor | ||||
---|---|---|---|---|
|
Phase | Stage | Timeframe | Status | Activity | Impact on Cornell AWS Account VPC Networks | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Preparation | Data Collection | November 2022 |
| none | |||||||||||||||
Resource Tagging |
|
| none | ||||||||||||||||
Resource Groups |
| none | |||||||||||||||||
Customer Input #1 | - |
| none | ||||||||||||||||
Migration | Transit Gateway Attachments | - |
| none | |||||||||||||||
Customer Input #2 | - |
| none | ||||||||||||||||
v2 BGP Updated | 16
| 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 7am |
| Azure | for campus-to-AWS | trafficcampus-VPC traffic may begin to use the v2 architecture (in just the one direction). This is limited only to Azure-to-AWS-VPC traffic will be routed through the V2 architecture | Cleanup | Customer Account Cleanup | - |
| none | Campus Direct Connect Cleanup |
| none |
FAQs
due to Cornell's network architecture. | |||||
VPC Routing Updated | 9am |
|
| ||
Campus Direct Connect Routes Updated | 9am |
|
| ||
Cleanup | Customer Account Cleanup | - |
| none | |
Campus Direct Connect Cleanup |
| none |
Anchor | ||||
---|---|---|---|---|
|
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.
Anchor | ||||
---|---|---|---|---|
|
Both the "VPC Routing Updated" and the "Campus Direct Connect Routes Updated" steps have simple rollback mechanism. 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.
- The rollback for the "VPC Routing Updated" step is to reassign the original Route Tables to the public and private subnets. This will rollback takes effect immediately.
- The rollback for the "Campus Direct Connect Routes Updated" step is to the cancel the failover of the Direct Connect Virtual Interfaces that we triggered to initial the campus routing updates. This rollback takes 5-20 minutes to complete.
FAQs
How do I tell if my AWS account will be affected How do I tell if my AWS account will be affected by this change?
The list of AWS accounts affected by this migration is here: Cornell AWS Accounts Affected by 2023 Direct Connect Architecture Migration
...
The exact pathways that Direct Connect traffic takes will change between the v1 and v2 architectures. But, the starting point (e.g., your VPC) and endpoint (e.g. a campus VLAN) of this traffic will constant.
When, specifically, will this migration occur?
...
) of this traffic will constant.
When, specifically, will this migration occur?
See detailed schedule above.
Is there any flexibility in migration dates?
Yes. See Alternate Migration Days above.
Can the migration be rolled back?
Yes. Each of the two active migration steps ("VPC Routing Updated" and "Campus Direct Connect Routes Updated") can be individually rolled back for each migrating AWS VPC. See Rollback above
...
.
What if I use Terraform or a similar tool to manage the network resources in my AWS account?
...
- Cornell Documentation
- Cornell AWS Accounts Affected by 2023 Direct Connect Architecture Migration
- Terraform Configuration Guidance for 2023 Direct Connect Architecture Migration
- Cornell AWS Direct Connect Routing Diagrams
- Announcements
- 2023-01-16 AWS Direct Connect Architecture Migration Execution
- 2023-01-10 AWS Direct Connect Architecture Migration Customer Review and Feedback #2
- 2022-12-20 AWS Direct Connect Architecture Design Update
- 2022-12-15 AWS Direct Connect Architecture Migration Customer Review and Feedback
- 2022-12-09 AWS Direct Connect Architecture Migration Preparation Continues
- 2022-11-02 Upcoming AWS Direct Connect Changes
- External Documentation
...