- Newest
- Most votes
- Most comments
Hello.
If VPC peering is already set up, I think option B will be the lowest cost.
TransitGateway must create an attachment for each VPC, which incurs $0.05 per attachment.(TransitGateway attachment pricing varies by region.)
Therefore, if communication routes to each VPC have already been secured through VPC peering, this may result in unnecessary costs.
I also don't recommend creating a ClientVPN endpoint for each AWS account, as it costs more than creating one in the main VPC.
If there are plans to add more VPCs in the future, it would be worth considering the use of Transit Gateway. However, if there are currently no plans to increase the number of VPCs, it would be better to continue using the existing VPC peering for communication.
https://aws.amazon.com/transit-gateway/pricing/?nc1=h_ls
Relevant content
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Agree with B