AWS / Tintri

Configure VPC to communicate with Private Network

tapasmahanta124Leave a comment

To allow a Virtual Private Cloud (VPC) to communicate with your private on-premise network, you can set up a Site-to-Site VPN connection or use Direct Connect (in AWS) or its equivalent in other cloud providers. In this scenario, we’ll consider AWS as an example, and we’ll set up a Site-to-Site VPN connection.

Prerequisites:

  • An AWS account.
  • A VPC created in AWS.
  • A Customer Gateway representing your on-premise network.
  • A Virtual Private Gateway attached to your VPC.

Steps to Setup Site-to-Site VPN Connection in AWS:

1. Create Customer Gateway

  • In AWS Console, navigate to VPC.
  • In the left navigation pane, go to Customer Gateways, then Create Customer Gateway.
  • Enter the public IP of your on-premise VPN device and choose the routing type.
aws ec2 create-customer-gateway --type ipsec.1 --public-ip-address [Your_On-Premise_Public_IP] --device-name MyCustomerGateway

2. Create Virtual Private Gateway & Attach to VPC

  • In AWS Console, go to Virtual Private Gateway, then Create Virtual Private Gateway.
  • Attach this to your VPC.
aws ec2 create-vpn-gateway --type ipsec.1 --amazon-side-asn 65000

# Note down the VPN Gateway ID and attach it to the VPC
aws ec2 attach-vpn-gateway --vpc-id [Your_VPC_ID] --vpn-gateway-id [Your_VPN_Gateway_ID]

3. Create Site-to-Site VPN Connection

  • Go to Site-to-Site VPN Connections, then Create VPN Connection.
  • Select the Virtual Private Gateway and Customer Gateway created in the earlier steps.
aws ec2 create-vpn-connection --type ipsec.1 --customer-gateway-id [Your_Customer_Gateway_ID] --vpn-gateway-id [Your_VPN_Gateway_ID] --options '{"StaticRoutesOnly":true}'

4. Configure On-Premise VPN Device

  • Once the VPN Connection is created, download the Configuration file provided by AWS.
  • Use this configuration to set up your on-premise VPN device with the appropriate settings, including IP addresses, shared keys, and routing.

5. Update Route Tables

  • Update the route tables associated with your VPC and on-premise network to route traffic intended for the other network through the VPN connection or Virtual Private Gateway.

6. Test Connectivity

  • Once everything is configured, test the connectivity by pinging a private IP in your VPC from your on-premise network and vice versa.

Conclusion:

These are high-level steps and examples of AWS CLI commands to set up a Site-to-Site VPN connection in AWS to connect a VPC to an on-premise network. Depending on the complexity of your network and security requirements, additional configurations and security measures might be needed.

Remember to replace placeholder values in the example commands with the actual IDs and values from your setup. Additionally, consult the documentation of your on-premise VPN device for specific configuration steps related to your device model.

This example assumes a Site-to-Site VPN connection using AWS services. Other cloud providers may have equivalent services and steps for configuring connectivity between VPCs and private on-premise networks.

Leave a comment