Launch a gateway¶
Click Gateway at navigation panel. Click New to launch a gateway. To launch a gateway with OpenVPN® capability, refer to this link.
Select Gateway Size¶
When selecting the Gateway Size, note the following guidelines of IPSEC performance based on iperf tests conducted between two gateways of the same size:
- t2 series throughput is not guaranteed; it can burst up to 130mbps.
- m3 series are in the range 300 - 500mbps
- m4.xlarge or c4.xlarge: approximately 500mbps
- c3.2xlarge or m4.2xlarge: approximately 1Gbps
- c3.4xlarge: approximately 1.2Gbps
- c4.2xlarge: 1.2Gbps - 1.5Gbps
if you need IPSEC performance beyond 1.2Gbps, refer to Cluster Peering.
Specify a Reachable DNS Server IP Address¶
Aviatrix gateway is launched with a default public DNS server IP address 220.127.116.11 to make sure the gateway has access to AWS public resources such as SQS for Controller and gateway communication. If you want to change to a different DNS server, select the box for “Specify a Reachable DNS Server IP Address” to enter an alternative DNS IP address.
Aviatrix gateway performs NAT function when this option is selected.
Allocate NEW EIP¶
When this optioin is selected, Aviatrix gateway allocates a new EIP for the gateway from AWS. When this optino is unchecked, the gateway select one allocated but unassociated EIP from the AWS account from which the gateway is launched.
When this option is selected, Aviatrix gateway is used for SSL VPN termination. It supports OpenVPN® client and Aviatrix client. For more details, check out this link.
If a gateway is launched with Designated Gateway enabled, the Aviatrix Controller programs the RFC1918 address ranges in the route table to point to the gateway instance. These routing entries are 10.0.0.0/8, 192.168.0.0/16 and 172.16.0.0/12. The Controller will not add additional route entries that is within this RFC1918 range when configuring Transit VPC, site2cloud or encrypted peering. However, if the address range is outside the RFC1918 the Controller will add these routes to point to the gateway.
Starting Release 3.0, gateway security policy page has been moved Security -> Stateful Firewall. Check out this guide.
There are two types of high availabiity on Aviatrix: “Gateway for High Availability” and “Gateway for High Availability Peering”.
“Gateway for High Availability Peering” is used for “Enable HA” field at Encrypted Peering configuration.
“Gateway for High Availability” is used when you need HA for a Transitive Peering.
You can change Gateway Size if need to change gateway throughput. The gateway will restart with a different instance size.