Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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

...

The 2023 Direct Connect architecture supports DC connectivity in multiple, but limited AWS regions. Transit Gateways are are regional, but TGWs in different regions can be peered. We use the TGW in us-east-1 as a "hub" and consider the TGWs in other regions as "spokes". This allows any VPC connected to any TGW to reach any other connected VPC. The TGWs in each region receive Direct Connect connectivity by connecting to a single Direct Connect Gateway (DCGW) which has a global footprint and can support TGW connections in any region. Technically, each DCGW is limited to attaching to no more than 3 TGWs. However, Cornell has received a special allowance that allows 5-6 TGW attachments per DCGW.

The cost to Cornell of supporting TGWs in each region is about $864 region/yr.

...