...
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.
...
The management and routing simplification offered by the v2 architecture comes with a modest change in costs seen by Cornell AWS accounts using Direct Connect.
V1 Architecture
Cornell AWS accounts using Direct Connect will no longer see these charges:
- Bandwidth charges for traffic from VPCs to campus using the Direct Connect is charged at $0.02/GB.
- Bandwidth charges from traffic TO VPCs from campus is free.
V2 Architecture
These charges are new to Cornell AWS customers using Direct Connect:
- Every VPC connected to the Transit Gateway will be charged $0.05/hr.
- Bandwidth charges for traffic from the VPC to the TGW is $0.02/GB.
- Bandwidth for traffic from the TGW to the VPC is free.
Summary
In total, Cornell AWS accounts using Direct Connect should not experience any significant change in bandwidth-related charges for VPC traffic bound for the campus. But, these AWS accounts will see an increase in Direct Connect-related costs of about $36/mo for each VPC connected to the v2 Direct Connect architecture.
If you have concerns about these cost changes, please contact cloud-support@cornell.edu.
| Anchor | ||||
|---|---|---|---|---|
|
...