We will complete the following tasks in our Azure portal:
CREATING A LOCAL CLOUD ENVIRONMENT WINDOWS
Windows and Linux VMs across Azure and AWS to establish and test our Site-to-Site (S2S) VPN connectivity.If you do have DNS servers, enter these details in your Virtual Network settings > DNS servers In my lab environment, I don’t have any custom DNS Servers.When configuring a Site-to-Site connection, public-facing IPv4 IP addresses are required for your VPN device.You need to have valid subscriptions in both the Azure and AWS environment.There are other appliances that can do this job as well and for more information around the supported Azure Site-to-Site VPN devices please refer to this link: Pre-requisites I chose to build out my solution by implementing a Windows Server with Routing and Remote Access service (RRAS) in AWS as my VPN device. Due to this limitation, the AWS environment requires an appliance or a supported VPN device. The Azure VPN Gateway will act both as initiator or responder for VPN access, but the AWS Gateway can only act as a responder.In the ideal world, the Azure VPN Gateway and AWS Gateway offering should have been enough to establish the VPN connection. I would like to share the steps I used to establish the VPN (Site-to-Site) tunnel between Azure and AWS. This allowed me to work on establishing a VPN tunnel between the two public cloud offerings. Recently, I was working with a client who utilises both AWS and Azure in their business and needed to establish a VPN connection across these cloud providers for certain services.