Using VPC Peering in addition to Transit Gateway for cost optimization
A Customer is planning to migrate to Amazon EKS, but will be operating their clusters in parallel for a while. They will be leveraging Transit Gateway (TGW) to connect to other VPCs, where database and auxiliary services live.
The question is if it is worth it to use VPC Peering in addition to connecting the two cluster VPCs with each other instead of using the TGW for that traffic, as that might be more cost effective.
It's (always) a trade off between cost and complexity, so it depends.
In this case the additional cost arises just from the TGW attachment cost, which (depending on the use-case) can be marginal. Customer should do a calculation to understand the financial advantage and factor in the added complexity as well.
Then, it will be up to them to decide whether or not the financial advantage justifies the added complexity or not.
Relevant questions
Cross Region private link
Accepted Answerasked 3 months agoVPC peering with a VPC from a different AWS Organization - cost implications
Accepted Answerasked 2 years agoMulti Account Connectivity using PrivateLink and/or Transit Gateway along with Direct Connect
Accepted Answerasked 3 years agoTransit Gateway Inter-region Peering Pricing
Accepted AnswerMulticast in Outposts through Transit Gateway or Local Gateway
Accepted Answerasked 2 years agoAWS Transit Gateway Routing Features
Accepted Answerasked 3 years agoSharing files between VPCs
Accepted Answerasked 3 years agoMoving to AWS Transit Gateway from VPC Peering
Accepted Answerasked 2 years agoUsing VPC Peering in addition to Transit Gateway for cost optimization
Accepted Answerasked a year agoWorkaround to overlapping IP address range
Accepted Answerasked 3 years ago