This new architecture simplifies Direct Connect configuration and management, and improves Direct Connect bandwidth and flexibility.
The migration process is designed to avoid interruption of Direct Connect connectivity, how brief interruptions may occur.
Cornell AWS account owners/administrators will be solicited for feedback directly via email several times throughout this process. But, in most cases, this input is not required for the migration to proceed.
AWS accounts having VPCs using Direct Connect and with numerous subnets and route tables, or where network resources are configured by infrastructure-as-code will need to provide input to complete this migration.
While line items for charges to Cornell AWS accounts will change between the old and new Direct Connect architectures, the overall change in cost is negligible.
CIT will be paying for new costs of ~$36/mo for each customer VPC connected the new Direct Connect architecture.
Table of Contents
...
Introduction
Excerpt
This document provides details about the Direct Connect architecture migration Cornell will be executing in early 2023.
Rationale
Cornell AWS accounts usingDirect Connectfor private access to Cornell networks will be transitioned to usingInternet 2 Cloud Connect(I2CC) as the Direct Connect provider.
The Internet 2 Direct Connect provider offers several benefits:
Consolidating and simplifying configuration and management of Direct Connect for Cornell AWS accounts
Improving flexibility and bandwidth of Direct Connect connectivity
Allows private Cornell network traffic in AWS and Azure to flow between those clouds without transiting campus
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.
