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.
Cross Region private linkAccepted Answerasked 3 months ago
VPC peering with a VPC from a different AWS Organization - cost implicationsAccepted Answerasked 2 years ago
Multi Account Connectivity using PrivateLink and/or Transit Gateway along with Direct ConnectAccepted Answerasked 3 years ago
Transit Gateway Inter-region Peering PricingAccepted AnswerEXPERTasked 2 years ago
Multicast in Outposts through Transit Gateway or Local GatewayAccepted Answerasked 2 years ago
AWS Transit Gateway Routing FeaturesAccepted Answerasked 3 years ago
Sharing files between VPCsAccepted Answerasked 3 years ago
Moving to AWS Transit Gateway from VPC PeeringAccepted Answerasked 2 years ago
Using VPC Peering in addition to Transit Gateway for cost optimizationAccepted Answerasked a year ago
Workaround to overlapping IP address rangeAccepted Answerasked 3 years ago