Bridging Azure and GCP: Setting up a Site-to-Site VPN
Bridging Azure and GCP: Setting up a Site-to-Site VPN
Transitioning infrastructure between cloud providers is a common venture in today's dynamic tech landscape. One such journey we embarked on was moving from Azure to GCP. The twist? Establishing a seamless connection between Azure and GCP, especially when dealing with Cloud SQL's unique VPC peering behavior. Dive into our guide to understand the intricacies and set up your VPN connection.
Azure Side Configuration:
Resource Group Formation:
Start afresh with a new resource group or harness the power of an existing one.
2. Virtual Network Creation:
Define your virtual network. Choose your resource group, name the network, pick a region, set the IPV4 address, and designate a subnet.
3. Virtual Network Gateway:
Time to establish the virtual network gateway. Here's what you'll need:
Subscription details, a unique name, region, gateway specifics, VPN particulars, SKU details, the previously created virtual network, gateway subnet details, public IP configurations, availability zones, BGP settings, and the BGP peer IP.
GCP Side Configuration:
VPC Initialization:
Either craft a new VPC or utilize an existing setup.
2. VPN Gateway Creation:
Assemble your VPN gateway. Here’s your checklist: VPN gateway name, network, region, and VPN tunnel's IP stack type.
3. VPN Tunnel & Peer VPN Gateway:
Set up the VPN tunnel. Remember to opt for the 'on-prem or non-google cloud' option for the peer VPN gateway.
Craft a new peer VPN gateway, adding details like the name, interfaces, and Azure's virtual network gateway IP.
4. Cloud Router and BGP Session:
Create a cloud router, ensuring the ASN number differs from Azure's.
Initiate a BGP session, inputting details such as name, Azure's ASN number, and BGP IPV4 address.
Back to Azure for the Final Touches:
Local Network Gateway:
Create this by selecting the resource group, region, naming the gateway, setting the endpoint IP as the GCP VPN Gateway IP, and defining the GCP subnet range.
2. BGP Configuration:
Opt for the BGP settings and input GCP's cloud router ASN number and router BGP IP.
3. Connection Formation:
Establish a connection within the virtual network gateway. Essential details include name, connection type, virtual network gateway, local network gateway, and the shared key from GCP.
Once everything is in place, Azure should display a "Connected" status, and GCP should mark the tunnel as "Established" and the BGP session as "BGP Established."
Voila! Your Azure VNet and GCP VPC are now interconnected. Stay tuned for our subsequent guide where we delve into setting up replication from Azure SQL to Cloud SQL.
Comments