You are a big fan of open source and don’t want to pay for commercially available VPN services.įirst, you’ll need to have VPCs configured with both public and private subnets in at least two different AWS regions.You have deployed high-availability architecture across VPCs but need to maintain direct, private communication between them.
You would like to regularly transfer data over a secure tunnel.You have a c onfigured disaster recovery setup in another region and want to connect using private communication.OpenVPN’s SSL/TLS based user-space VPN supports Linux, Solaris, OpenBSD, FreeBSD, NetBSD, Mac OS X, and Windows 2000/XP. If your organization can’t afford commercial VPN’s like a commercial product from Cisco or an on-premise UTM appliance, you can use the open source OpenVPN package to secure communications between your distributed resources at no cost. But what if you want to connect instances hosted in separate AWS regions? OpenVPN can make it happen. You can also directly connect instances in two separate VPC’s within a single region using VPC Peering.Īssuming that you’ve set up your subnets so they don’t overlap, a peering connection enables direct traffic routing between VPCs using private IP address ranges. Using OpenVPN free to secure communications between distributed resources.Īs you know, multiple AWS instances living within a single VPC can communicate with each other using private IP addresses.
0 kommentar(er)
