...
This document provides details about the Direct Connect architecture migration we will be executing in early 2023.
Rationale
Cornell AWS accounts using Direct Connect for private access to Cornell networks will be transitioned to using Internet 2 Cloud Connect (I2CC) as the Direct Connect provider. That change will simplify configuration and management of Direct Connect for AWS accounts. This switch to I2CC Direct Connect also will allow private Cornell network traffic in AWS and Azure to flow between clouds without transiting campus, as it does prior to this migration.
Scope
As of , 65 Cornell AWS accounts were configured to use Direct Connect. During this migration, all those AWS accounts will have their existing Direct Connect connectivity updated to use new pathways and AWS resources to connect the Cornell campus network to AWS.
...
| Info |
|---|
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. |
Costs
The management and routing simplification offered by the v2 architecture comes with a modest increase costs seen by Cornell AWS accounts using direct connect. Every VPC connected to the Transit Gateway will be charged $0.05/hr plus a $0.02/GB for bandwidth through the TGW.
Migration Process
draw.io source: direct-connect-migration-process.v2.drawio
...