Costs analysis for Data Transfer via VMware Managed TGW

-

Gilles Chekroun


Lead VMware Cloud on AWS Solutions Architect
---
Every customer design is different but all of them should include a costs analysis specifically when using VMware managed Transit Gateway or AWS Transit Gateway.
The AWS page here has very useful information for us to be able to understand costs.

Transit Gateway Costs

TGW pricing is split in 2 components:
  • A fixed price for infrastructure connectivity per hour.
    • Depending on the attachments, various account owners are charged. 
  • A variable price for processing data via the TGW.
    • Price is per GB.
    • The sending account is charged.
Prices depend on regions and range from $0.05 to $0.09 per attachment per hour.

Who is charged?

See AWS page

VPC attachments

The VPC account owner is charged and is billed hourly.

VPN attachments

The TGW account owner is billed hourly.
Site-to-Site VPN connection pricing still applies in addition to the VPN TGW attachments.

Direct Connect Gateway attachments

The DXGW account owner is billed hourly.

Peering Attachments

Each Transit Gateway account owner is billed hourly for the peering attachment with the other Transit Gateway.

Prices

For most USA regions and Dublin, TGW attachments are $0.05 per hour.
For North California and Europe, $0.06 per hour.
Other regions have different prices. Check here.
Each partial hour consumed is billed as a full hour.

Data processing Charges

Data charges are the same for all regions. $0.02/GB.
Data processing charges apply for each GB sent from a VPC, Direct Connect or VPN to the TGW.
There are NO Data charges for data sent from a peering attachment to another TGW however, data transferred over a peering attachment incurs the standard inter-region data transfer charges (egress at $0.02/GB – ingress free).

Examples

In the various examples below, we will consider USA regions and a transfer of 1 GB of data.

SDDCs via VMware managed TGW 

Attachments

2 x $0.05 /hour, or $72 per month

Data Processing

SDDC1 account charged $0.02/GB

SDDC to VPC via VMware managed TGW 

Attachments

2 x $0.05 /hour or $72 per month

Data Processing

SDDC1 account charged $0.02/GB

SDDCs via transit VPC (Single region) 

Attachments

4 x $0.05 /hour or $144 per month

Data Processing

SDDC1 account charged $0.02/GB
Transit VPC account charged $0.02/GB 

SDDCs to VPC via Transit VPC and TGW (Single region) 

Attachments

4 x $0.05 /h or $144 per month

Data Processing

SDDC1 account charged $0.02/GB
Transit VPC account charged $0.02/GB 

Detailed description with Multi AWS accounts

SDDCs via peered VMware managed TGWs (Multi regions) 

Attachments

4 x $0.05 /h or $144 per month

Data Processing

SDDC1 account charged $0.02/GB
vTGW1 account charged $0.02/GB for egress inter-region (region A)
vTGW2 not charged as data is ingress for region B

SDDC to VPC via peered TGWs (Multi regions - future VMC release) 

Attachments

4 x $0.05 /h or $144 per month

Data Processing

SDDC1 account charged $0.02/GB
vTGW1 account charged $0.02/GB for egress inter-region (region A)
AWS TGW not charged as data is ingress for region B


Thanks for reading.


Comments

Post a Comment

Populars

Egress VPC and AWS Transit Gateway (Part1)

-
Image
Gilles Chekroun
 Lead VMware Cloud on AWS Solutions Architect --- Usually my blog posts are customer driven and recently I have been working on a design that would include an Egress VPC and AWS Transit Gateway. This customer is going to use both VMware Managed Transit Gateway and also AWS Transit Gateway. I will split this post in 3 parts: The Egress VPC - this article Adding a VMC SDDC to the Egress VPC here Adding VMware Managed Transit Gateway here Why do we need an Egress VPC? Numerous posts on AWS site  will describe how to build an Egress VPC and the subtleties of the various route tables of the TGW and the Egress VPC itself. The main goal is to have ONE Internet gateway only  that will allow workloads to go out to internet on the Egress VPC. One of the most important point is redundancy and multi-availability zones. Applications usually reside in private subnets, while NAT Gateways reside in a public subnet. NAT Gateways To focus the Internet access to a single point, we can cre
Read more

AWS Transitive routing with Transit Gateways in the same region

-
Image
Gilles Chekroun Lead VMware Cloud on AWS Specialist --- At the AWS Re:invent 2019 conference, the long waited TGW peering functionality was announced and available in a few AWS regions. This is an INTER-REGION peering only meaning that the Transit Gateways need to be in different regions. Hoping that AWS will soon release an INTRA-REGION capability I discussed with a few AWS Solutions Architects in Las Vegas, among them Tom Adamski , about using a VPC as a bridge between two TGWs in the same region. Tom assured me that it is possible opening for the first time the transitive routing capability in AWS networking. Well . . . I needed to test that and see by myself. Test bed For a simple test, I will use 2 TGWs in the same regions with 2 VPCs attached each and another VPC as "bridge" connected to both TGWs. Yes you can connect a VPC up to 5 TGWs . The whole idea is to use this "bridging VPC" and point the default route of the TGWs to it. To do that I c
Read more

Considerations on vTGW to TGW Peering Link

-
Image
   Gilles Chekroun
 Lead VMware Cloud on AWS Solutions Architect --- Recently I was talking with a Customer on designing their VMware Cloud on AWS environment and linking it to their existing AWS infrastructure. The idea was to have 2 SDDCs, Test and Prod, and link them with a VMware Managed TGW and peer it to their existing TGW. The customer requirements were: VMs in each SDDC should have internet access from the SDDC out VMs from Test should be able to talk to VMs in Prod VMs in any SDDC should be able to access their own vCenter but also the other one Some VMs any SDDC should have a Public IP and NAT rule to be accessible from outside VMware traffic should stay within VMware SDDCs Other traffic, like on-prem, should go via the Customer TGW Test Setup Step1 - Create SDDC Group Create an SDDC Group and attach the 2 SDDCs Prod and Test Make sure the proper FireWall rules are open in each SDDC Compute GW. Step 2 - Attach the Customer TGW In the SDDC Groups, under External TGW TAB, add t
Read more