Consolidating and simplifying configuration and management of Direct Connect for Cornell AWS accounts (compared to the previous on-campus Direct Connect architecture)
Improving flexibility and bandwidth of Direct Connect connectivity
Allowing private Cornell network traffic in AWS and Azure to flow between those clouds without transiting campus

Info

Cornell campus is connected to NYSERNET/I2 via two separate physical links, each 100Gbps. One link runs to Buffalo, and one runs to New York City.
I2 to Azure linkage is dual connectivity, with a physical maximum of 5Gbps. The actual capability of the I2-Azure link is limited by Express Route bandwidth configuration.
As of January 2023, Cornell does not have a I2CC link to GCP.
The 5Gbps connectivity between I2 and Azure/AWS is infrastructure shared with other I2CC customers.
See also the physical configuration details here: https://mapper.cit.cornell.edu/g46967a52/document/_/!index.html

Direct Connect + Transit Gateway Architecture

...

Space shortcuts