This section provides detailed step-by-step instructions for using AWS Site-to-Site VPN and AWS Transit Gateway as a means to establish network connectivity between your on-premises and AWS environments.
By following these instructions, you will enable network connectivity between your on-premises environment and the centrally managed development VPC you established earlier in this guide.
Later in this guide, when you set up your test and production VPCs, the steps required to enable those VPCs to reuse your site-to-site VPN connection will be addressed. The process in your AWS environment will be largely a repeat of the steps in this section that are used to connect your development VPC to your on-premises network.
Simulating on-premises customer gateway: If you’re either experimenting with AWS Site-to-Site VPN connections or demonstrating how they work, you can easily simulate a customer on-premises environment and customer gateway. See the AWS Blogs post Simulating Site-to-Site VPN Customer Gateways Using strongSwan for details on setting up an open source based VPN gateway in a separate VPC that simulates an on-premises environment. If you’d like to experiment with certificate-based authentication and site-to-site VPN, see the VPN Gateway Stack Using strongSwan project on GitHub.com.
Automated solution: As you expand the number of VPCs in your AWS environment, you may benefit from implementing the Serverless Transit Network Orchestrator AWS solution. This solution automates much of the work required to integrate newly created VPCs with your transit gateway.