| Table of Contents |
|---|
...
Introduction
Beginning May 2016 Cornell AWS accounts are setup with AWS Direct Connect (DC) joining the campus 10-space network to the 10-space network in Cornell Standard AWS VPCs. Prior to that accounts were setup with VPN connection back to campus.Direct Connect is a service that Cornell uses to extend the private Cornell network into Cornell AWS accounts, giving VPCs connectivity to the entirety of the private Cornell network (10.0.0.0/8) and optionally the Cornell public network (i.e., public CIDR blocks).
When Cornell AWS accounts need access to the Cornell network, a Cornell Standard AWS VPC is created in the Cornell AWS account and linked to the Cornell network using Direct Connect.
If you already have a Cornell AWS account and would like to add access to the Cornell private network to it, send a request to cloud-support@cornell.edu.In early 2023 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 now. See Upcoming AWS Direct Connect Changes
Cornell Direct Connect Documentation
| Children Display | ||||||
|---|---|---|---|---|---|---|
|
References
- 2023-01-19 AWS Direct Connect Architecture Migration Completed
- 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