- Newest
- Most votes
- Most comments
Hey Vijaygvasan!
I'm curious as to what your use case is that you decided to use OpenVPN to connect AWS accounts together. If you have resources in different VPC's that need to communicate with each other (within or across accounts), you can utilize VPC Peering. VPC Peering allows for connectivity between different VPC's, essentially extending your private network. For a small amount of accounts, in your case 3, this would be perfect, especially if you're trying to maintain a connection to account A without inadvertently creating a connection between accounts B and C. Creating a VPC peering connection is free, but keep in mind data transfer charges could still apply.
If however, your AWS footprint grows and you would like to extend connectivity across different VPC's in a transitive manner, then we also have a Transit Gateway that makes it very easy to administer and handle connections to different VPCs, similar to VPC Peering, but in a hub-spoke model.
Here are some helpful links: What is VPC Peering: https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html VPC Peering to different accounts: https://docs.aws.amazon.com/vpc/latest/peering/create-vpc-peering-connection.html#different-account-same-region Transit Gateway: https://aws.amazon.com/transit-gateway/
Hope this helps!
Relevant content
- asked 7 months ago
- asked 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago