*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
Cornell AWS accounts using Direct Connect see these Direct Connect-related charges in the 2023 architecture:
- FREE
- Bandwidth There is no charged for traffic FROM the Transit Gateway TO VPCs is free. Depending on where the traffic originated, customers may see charges for traffic prior to it entering the Transit Gateway.
- FREE to Cornell AWS Accounts
- 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 Transit Gateway attachment automatically will automatically direct those charges to a CIT KFS account. This charge accounts for about $36/mo.
- CUSTOMER COST
- Bandwidth charges for traffic FROM VPCs TO the Transit Gateway is Gateway 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.
Costs of Peering Versus Transit Gateway Use
...
- Bandwidth charges for traffic originating in VPCs FROM the Transit Gateway TO campus using the Direct Connect is charged at $0.02/GB.
- This means that the total cost for traffic from VPCs to campus via the Transit Gateway and Direct Connect is $0.04/GB.
| Info |
|---|
Even though the 2023 Direct Connect architecture fully interconnects all VPCs using Direct Connect (i.e., attached to the Transit Gateway), |
...
establishing peering directly between VPCs |
...
can cut costs because peering connections have no bandwidth charges. See Peering AWS VPCs that Use Direct Connect. |
Document Change Log
| Date | Description |
|---|---|
| Added information about the customer costs for traffic originating from customer VPCs crossing the Direct Connect to campus. |
When to setup peering:
- High-volume data transfer
- Ultra-low latency data transfer – Traffic using peering connections makes exactly one hop. Traffic using a Transit Gateway makes about four hops.
- When Security Groups in one VPC need to reference Security Groups in the peered VPC. – Transit Gateway connectivity does not support this cross-VPC Security Group references.
- When one of the VPCs is not connected to the Transit Gateway (and thus not using Direct Connect).
When to avoid peering:
...