...
| Info |
|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
The management and routing simplification offered by the v2 architecture comes with a shift in costs seen by Cornell AWS accounts using Direct Connect, but the overall impact to Cornell AWS account costs should be negligible.
V1 Architecture
Cornell AWS accounts using Direct Connect saw these Direct Connect-related charges:
Bandwidth charges for traffic from VPCs to campus using the Direct Connect is charged at $0.02/GB.This cost is born by each Cornell AWS account using Direct Connect in the v1 architecture. This cost will no longer be present using the v2 architecture.
Bandwidth charges from traffic TO VPCs from campus is free.
V2 Architecture
These charges are involved in the v2 architecture:
Every VPC connected to the Transit Gateway is charged $0.05/hr by AWS. These charges will appear in customer AWS account invoices, but the charges will be paid for by CIT since a Cost Center tag on the TGW attachment automatically will automatically direct those charges to a CIT KFS account.Bandwidth charges for traffic from the VPC to the TGW is $0.02/GB. This cost is born by the customer and the magnitude of the charge will be similar to the Direct Connect egress charges born by the customer in the v1 architecture.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 charges for using the v2 Direct Connect architecture. The one new cost that customers will see on invoices is being paid by CIT through the use of a Cost Center tag on the relevant resources.
| Anchor | ||||
|---|---|---|---|---|
|
...