- Newest
- Most votes
- Most comments
Thank you for the answer. The 2 TGW in the same region are needed because each hub account (and the connected VPC spokes) are managed by different MSP with different NVA/policies etc. I am getting confussed on the charges that will occur after traffic arrives on second TGW. TGW will process the traffic (if process means check TGW RT and forward) 2 times. One to send to security VPC and one to send from security VPC to destination. I understand that will charge 2*0.02$. Also what about charges of the return traffic.
Why do you want to use 2 TGWs in a single region? Note below 2 points from Transit gateway design best practices
- You do not need additional transit gateways for high availability, because transit gateways are highly available by design.
- For redundancy, use a single transit gateway in each Region for disaster recovery.
If you still decide to go ahead with 2 TGWs, data sent over the peering attachment to TGW2 does not incur data processing charges, as mentioned in the TGW pricing page
Data processing charges do not apply for data sent from a peering attachment to a Transit Gateway
Relevant content
- Accepted Answerasked 3 years ago
- asked 5 months ago
- asked 2 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
TGW2 will not incur charges, see this example in the pricing page (in your example there is no inter-region charge as both TGWs are in the same region): Transit Gateway data processing charge across peering attachments: 1 GB was sent from an EC2 instance #1 in a VPC attached to Transit Gateway #1 (N. Virginia region) over a peering attachment to Transit Gateway #2 (Oregon region), where it will reach EC2 instance #2 within a VPC. The total traffic related charges will result in a charge of $0.04. This charge comprises $0.02 for Transit Gateway Data Processing on Transit Gateway #1 along with $0.02 for outbound inter-Region data transfer charges. Here Transit Gateway #2 will not incur data processing charges, as they do not apply for data sent from a peering attachment to a Transit Gateway. As inbound inter-Region data transfer charges are free, no further charges apply to the Transit Gateway #2 (Oregon region) side.
Based on my TGW 2 routing table, traffic will flow first to firewall through a VPC attachment and then through another VPC attachment to final destination (workload server), nothing else will be charged? AWS example stays in a single hope after the TGW peering attachment.