{"id":250,"date":"2018-05-18T15:27:48","date_gmt":"2018-05-18T15:27:48","guid":{"rendered":"https:\/\/cloudmanagement.navisite.com\/?p=250"},"modified":"2020-01-08T04:24:35","modified_gmt":"2020-01-08T04:24:35","slug":"hybrid-cloud-connectivity-azure-p2s-vpn-s2s-from-azure-to-aws","status":"publish","type":"post","link":"https:\/\/www.navisite.com\/blog\/hybrid-cloud-connectivity-azure-p2s-vpn-s2s-from-azure-to-aws\/","title":{"rendered":"Hybrid Cloud Connectivity: Azure P2S VPN, S2S from Azure to AWS"},"content":{"rendered":"
<\/a><\/p>\n This is the fifth blog in the Azure Networking Blog<\/strong> series, and focuses on Azure P2S VPN functionality. Check out other blogs in this series:<\/p>\n In this blog post we will review various Hybrid Cloud Connectivity Options. The VPN Client allows the remote users to connect to Cloud private network through Internet from anywhere in the world. In Azure, this can be accomplished with a Point-to-Site VPN Gateway (Route-Based) with RADIUS Authentication. Azure P2S is a useful solution instead of a site-to-site when you have a few remote users that need connectivity into Azure. In the first part of this blog post, I will walk you through a use case with Azure P2S VPN<\/a><\/strong> using Active Directory Server configured with Radius Server role.1.\u00a0 <\/strong>Summary: Hybrid Cloud Connectivity – Azure P2S VPN<\/strong><\/h2>\n
\n
\nOne of our clients recently migrated from AWS to Azure. One way to connect the two clouds together is via an IPSec VPN tunnel. \u00a0We ran into compatibility issues between Azure and AWS while setting up the VPN tunnel, due the fact that AWS currently only supports ikev1, and Azure’s Route-Based VPN gateway only supports ikev2.
\nTo address overcoming this limitation, in the second half of the blog post we’ll take a look at a use case to connect AWS Cloud to Azure Cloud<\/a><\/strong> using StrongSwan (which serves as a Virtual Appliance on the AWS die) with ikev2 support, and using custom routing. \u00a0\u00a0This can also be accomplished with Windows Server (RRAS on the AWS side)
\nNote:<\/strong> This blog post assumes general familiarity with Azure cloud constructs (Resource Groups, VNets and Subnets), AWS networking constructs (VPC, Subnet, Instances and Route tables) and common networking concepts. Microsoft has some great documentation to assist with further understanding this process.
\nThis blog post is focused on end-to-end configuration blueprint, reference architecture and in-depth troubleshooting for the above two use cases.\u00a0 We will use this diagram as a reference architecture.
\n