In one of my projects, I met with a requirement where I was working on an application that follows a client-server architecture. There were servers connected to multiple clients. Initially, the Server was placed into AWS and the connected clients were also there, but after a couple of years our requirements got changed and a new business unit came into the picture with its own clients that were needed to be connected with the server present in the AWS cloud.<\/p>\n\n\n\n
Now, these new clients were present on Azure but the server was on AWS. Migration of server was not an option for us because our customer was not ready to migrate those clients from Azure to AWS, so this was a completely new use case, to which we decided to connect both the cloud providers with each other by setting up IPSec VPN tunnel.<\/p>\n\n\n\n Prerequisites for Implementing the Use Case<\/strong><\/strong><\/p><\/amp-fit-text>\n\n\n\n Architecture<\/strong><\/p>\n\n\n\n Our typical architecture for this use case looks as below:<\/p>\n\n\n\n Overview<\/strong><\/p>\n\n\n\n Generally, we create a site-to-site VPN<\/strong> for connecting the cloud network with the on-premise network. But for this kind of use case, we need to create a site-to-site VPN between two<\/strong> cloud providers.<\/p>\n\n\n\n Let me explain what we are going to do, and how we are going to implement a site-to-site VPN. <\/p>\n\n\n\n You need to follow the below steps to create a site-to-site VPN. <\/p>\n\n\n\n Step1: <\/strong>We will firstly start with creating a VPC at the AWS side in which we will create two subnets a public subnet and a private subnet.<\/p>\n\n\n\n In the process of filtering the traffic at the subnet level, you will need to create two NACL(Network Access Control List) and associate one with the private subnet, and another with the public subnet. Also do not forget to create two EC2, one private and one public instance. We will use the public EC2 as a bastion server to access the private EC2 instance.<\/p>\n\n\n\n Step 2:<\/strong> After creating the above component, please do not forget to create the routing rules since you also need to access your public EC2 instance from your local system, so for that, we will use the internet gateway which will help us to communicate with the public EC2 from our local computer. <\/p>\n\n\n\n Step3:<\/strong> Let’s move further and create a customer gateway, but it will be asking for an IP, and getting the Public IP of Virtual Network Gateway of Azure we need to jump into the azure and set up a Virtual Network Gateway from where we will be getting an option to generate a public IP. <\/p>\n\n\n\n <\/p>\n\n\n\n Step4: <\/strong>Now we have the Public IP of Azure Virtual Network Gateway, let’s create the Customer Gateway at the AWS Side. <\/p>\n\n\n\n Step5: <\/strong>After creating the customer gateway you need to also create the Virtual Network Gateway at the AWS side and attach the same with the VPC.<\/p>\n\n\n\n Step6:<\/strong> After Creating the Virtual Network Gateway at the AWS end, let’s create a site-to-site connection and download the generic configuration, the values of this configuration file will be needed to configure the Local Network Gateway and connection at the Azure end. <\/p>\n\n\n\n Step7: <\/strong>Now let’s jump into the azure end create a Private VM in the same Virtual network in which the Virtual network gateway is configured.<\/p>\n\n\n\n <\/p>\n\n\n\n Finally, we have configured everything that is needed to set up a site-to-site VPN between AWS and Azure so let’s jump into the private EC2 instance and ping the Private VM of Azure or you can also ping the private EC2 from the Azure VM.<\/p>\n\n\n\n Conclusion<\/strong><\/p>\n\n\n\n In this blog, we have learned about the prerequisites for creating the Site to Site VPN between AWS and Azure. Also, we have discussed the overview of connecting both Azure and AWS.<\/p>\n\n\n\n In the next blog, we will discuss the detailed steps required for creating the IPSec VPN tunnel between AWS and Azure till then please stay tuned and take care…Cheers!!!!!<\/p>\n\n\n\n Happy Learning!!!<\/p>\n\n\n\n Gif References: Gif1<\/a>, Gif2<\/a><\/p>\n\n\n\n Blog Pundit: <\/strong>Naveen Verma<\/strong><\/a> and<\/strong> Adeel Ahmad <\/strong><\/a><\/p>\n\n\n\n Opstree<\/strong> <\/a>is an End to End DevOps solution provider<\/p>\n\n\n\n![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/01\/connecting_azure_with_aws-page-1.jpg?w=771\")
<\/figure>\n\n\n\n\n\n\n\n![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/01\/connecting_azure_with_aws-page-2-3.jpg?w=976\")
<\/figure>\n\n\n\n![\"I](\"https:\/\/c.tenor.com\/8QZfcU8xcYwAAAAM\/i-have-your-ip-address.gif\")
<\/figure>\n\n\n\n<\/figure>\n\n\n\n
![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/01\/aws-to-azure-ping.png?w=874\")
<\/figure>\n\n\n\n