Comment on page
This guide will show you how to connect your AWS cloud to the GoodAccess Gateway via a site-to-site connection using the IPsec protocol.
Click + Add new, enter the Branch name and subnet, and select Gateway.
Choose IPSec Protocol, fill out the Settings configuration form, and click Save.
You may return to the configuration via the Edit button of your Cloud at any time.
Log in to AWS, and go to Services > VPC (you can use the searchbar).
Locating the VPC application
Go to Virtual Private Network (VPN) > Customer Gateways and click Create customer gateway.
Give the customer gateway a name and set the configuration as follows:
- BGP ASN - 65000
- IP address - IP of your GoodAccess Gateway
Click Create customer gateway to confirm your settings.
Menu of VPC > VPN
Creating a customer gateway
Go to Virtual Private Network (VPN) > Virtual Private Gateways and click Create virtual private gateway.
Give the virtual private gateway a name, and choose Amazon default ASN.
Click Create virtual private gateway to confirm your settings.
Select the newly created virtual private gateway and click Attach to VPC.
Creating a virtual private gateway
Attaching the virtual private gateway to VPC
Go to Virtual Private Network (VPN) > Site-to-Site VPN Connections and click Create VPN connection.
Give the VPN connection a name and set the configuration as follows:
- Target gateway type - Virtual private gateway
- Customer gateway - Existing
- Routing options - Static
Open Tunnel 1 options:
Click Create VPN connection to confirm your settings.
Creating a VPN connection
Setting up the Phase I & II configuration
Go to Virtual Private Cloud (VPC) > Route Tables. Click Edit routes and Add the following routes:
Don't forget to Save changes.
Editing the routes
Adding new routes
You have now successfully connected your AWS cloud to GoodAccess.
You may check the status of the connection in:
- GoodAccess - Control Panel > Clouds & Branches > Edit button > Test connection
- AWS - Virtual Private Network (VPN) > Site-to-Site VPN Connections
The configuration shows two tunnels created for the same VPN connection to AWS. We recommend using the first one.
If you have a second gateway and want backup, you can use the second tunnel for a high availability solution.