Professional Documents
Culture Documents
Connectivity Options
Steve Morad
July 2014
Amazon Web Services Amazon VPC Connectivity Options July 2014
Contents
Abstract 3
Introduction 4
Network-to-Amazon VPC Connectivity Options 5
Hardware VPN 7
AWS Direct Connect 8
AWS Direct Connect + VPN 10
AWS VPN CloudHub 11
Software VPN 13
Amazon VPC-to-Amazon VPC Connectivity Options 15
VPC Peering 17
Software VPN 19
Software-to-Hardware VPN 20
Hardware VPN 22
AWS Direct Connect 23
Internal User-to-Amazon VPC Connectivity Options 26
Software Remote-Access VPN 27
Conclusion 29
Appendix A: High-Level HA Architecture for Software VPN Instances 30
VPN Monitoring Instance(s) 31
Page 2 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Abstract
Amazon Virtual Private Cloud (Amazon VPC) lets customers provision a private, isolated
section of the Amazon Web Services (AWS) cloud where they can launch AWS
resources in a virtual network using customer-defined IP address ranges. Amazon VPC
provides customers with several options for connecting their AWS virtual networks with
other remote networks. This document describes several common network connectivity
options available to our customers. These include connectivity options for integrating
remote customer networks with Amazon VPC as well as connecting multiple Amazon
VPCs into a contiguous virtual network.
This whitepaper is intended for corporate network architects and engineers or Amazon
VPC administrators who would like to review the available connectivity options. It
provides an overview of the various options to facilitate network connectivity discussions
as well as pointers to additional documentation and resources with more detailed
information or examples.
Page 3 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Introduction
Amazon VPC provides multiple network connectivity options for you to leverage
depending on your current network designs and requirements. These connectivity
options include leveraging either the Internet or an AWS Direct Connect connection as
the network backbone and terminating the connection into either AWS or user-
managed network endpoints. Additionally, with AWS, you can choose how network
routing will be delivered between Amazon VPC and your networks, leveraging either
AWS or user-managed network equipment and routes. This whitepaper considers the
following options with an overview and a high-level comparison of each:
Hardware VPN Describes establishing a hardware VPN connection from your network equipment on a
remote network to AWS-managed network equipment attached to your Amazon VPC.
AWS Direct Connect Describes establishing a private, logical connection from your remote network to
Amazon VPC, leveraging AWS Direct Connect.
AWS Direct Connect Describes establishing a private, encrypted connection from your remote network to
+ VPN Amazon VPC, leveraging AWS Direct Connect.
AWS VPN CloudHub Describes establishing a hub-and-spoke model for connecting remote branch offices.
Software VPN Describes establishing a VPN connection from your equipment on a remote network to
a user-managed software VPN appliance running inside an Amazon VPC.
Amazon VPCtoAmazon VPC Connectivity Options
VPC Peering Describes the AWS-recommended approach for connecting multiple Amazon VPCs
within a region using the Amazon VPC peering feature.
Software VPN Describes connecting multiple Amazon VPCs using VPN connections established
between user-managed software VPN appliances running inside of each Amazon VPC.
Software-to- Describes connecting multiple Amazon VPCs with a VPN connection established
Hardware VPN between a user-managed software VPN appliance in one Amazon VPC and AWS-
managed network equipment attached to the other Amazon VPC.
Hardware VPN Describes connecting multiple Amazon VPCs, leveraging multiple hardware VPN
connections between your remote network and each of your Amazon VPCs.
AWS Direct Connect Describes connecting multiple Amazon VPCs, leveraging logical connections on
customer-managed AWS Direct Connect routers.
Internal User-to-Amazon VPC Connectivity Options
Software Remote In addition to customer networktoAmazon VPC connectivity options for connecting
Access VPN remote users to VPC resources, this section describes leveraging a remote-access
solution for providing end-user VPN access into an Amazon VPC.
Page 4 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Hardware Hardware-based, Reuse existing VPN equipment and Network latency, variability, and
VPN IPsec VPN processes availability are dependent on
connection over Reuse existing Internet connections Internet conditions
the Internet Customer-managed endpoint is
AWS-managed endpoint includes
multidata center redundancy and responsible for implementing
automated failover redundancy and failover (if
required)
Supports static routes or dynamic
Border Gateway Protocol (BGP) Customer device must support
peering and routing policies single-hop BGP (when
leveraging BGP for dynamic
routing)
AWS Direct Dedicated network More predictable network performance May require additional telecom
Connect connection over Reduced bandwidth costs and hosting provider
private lines relationships or new network
1 or 10 Gbps provisioned connections
circuits to be provisioned
Supports BGP peering and routing
policies
1
http://aws.amazon.com/vpc/faqs/
Page 5 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
AWS Direct Hardware-based, Same as the previous option with the Same as the previous option
Connect + IPsec VPN addition of a secure IPsec VPN with a little additional VPN
VPN connection over connection complexity
private lines
AWS VPN Connect remote Reuse existing Internet connections Network latency, variability, and
CloudHub branch offices in a and AWS VPN connections (e.g., use availability are dependent on
hub-and-spoke AWS VPN CloudHub as backup the Internet
model for primary connectivity to a third-party MPLS User-managed branch office
or backup network) endpoints are responsible for
connectivity AWS-managed virtual private gateway implementing redundancy and
includes multidata center redundancy failover (if required)
and automated failover
Supports BGP for exchanging routes
and routing priorities (e.g., prefer MPLS
connections over backup AWS VPN
connections)
Software Software Supports a wider array of VPN Customer is responsible for
VPN appliance-based vendors, products, and protocols implementing HA (high
VPN connection Fully customer-managed solution availability) solutions for all
over the Internet VPN endpoints (if required)
Page 6 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Hardware VPN
Amazon VPC provides the option of creating an IPsec, hardware VPN connection
between remote customer networks and their Amazon VPC over the Internet, as shown
in Figure 1. Consider taking this approach when you want to take advantage of an AWS-
managed VPN endpoint that includes automated multidata center redundancy and
failover built into the AWS side of the VPN connection. Although not shown, the
Amazon virtual private gateway (VGW) represents two distinct VPN endpoints,
physically located in separate data centers to increase the availability of your VPN
connection.
The VGW also supports and encourages multiple user gateway connections so you can
implement redundancy and failover on your side of the VPN connection as shown in
Figure 2. Both dynamic and static routing options are provided to give you flexibility in
your routing configuration. Dynamic routing leverages BGP peering to exchange routing
information between AWS and these remote endpoints. With dynamic routing, you can
also specify routing priorities, policies, and weights (metrics) in your BGP
advertisements and influence the network path between your network(s) and AWS.
It is important to note that when BGP is used, both the IPSec and the BGP connections
must be terminated on the same user gateway device, so it must be capable of
terminating both IPSec and BGP connections.
Page 7 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Additional Resources
Adding a Hardware Virtual Private Gateway to Your VPC 2
Customer Gateway device minimum requirements 3
Customer Gateway devices known to work with Amazon VPC 4
2
http://docs.amazonwebservices.com/AmazonVPC/latest/UserGuide/VPC_VPN.html
3
http://aws.amazon.com/vpc/faqs/#C8
4
http://aws.amazon.com/vpc/faqs/#C9
Page 8 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
IP addresses. You can choose from an ecosystem of WAN service providers for
integrating your AWS Direct Connect endpoint in an AWS Direct Connect location with
your remote networks. Figure 3 illustrates this pattern.
Additional Resources
AWS Direct Connect product page 5
AWS Direct Connect locations 6
AWS Direct Connect FAQs 7
Getting Started with AWS Direct Connect 8
5
http://aws.amazon.com/directconnect/
6
http://aws.amazon.com/directconnect/#details
7
http://aws.amazon.com/directconnect/faqs/
8
http://docs.amazonwebservices.com/DirectConnect/latest/GettingStartedGuide/Welcome.html
Page 9 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Clients Clients
EC2 Instances
VPC Subnet 2
Remote
Availability Zone AWS Direct Servers
Connect Location Customer
Amazon VPC Remote Network
Additional Resources
AWS Direct Connect product page 9
AWS Direct Connect FAQs 10
Adding a Hardware Virtual Private Gateway to Your VPC
9
http://aws.amazon.com/directconnect/
10
http://aws.amazon.com/directconnect/faqs/
Page 10 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Figure 5 depicts the AWS VPN CloudHub architecture, with blue dashed lines indicating
network traffic between remote sites being routed over their AWS VPN connections.
Customer
Gateway
ASN: 6500
Customer Network
New York
EC2 Instances
Customer
VPC Subnet 1 Gateway
ASN: 6501
Availability Zone
Virtual
Customer Network
Private Los Angeles
Gateway
EC2 Instances
VPC Subnet 2
AWS VPN CloudHub leverages an Amazon VPC virtual private gateway with multiple
gateways, each using unique BGP autonomous system numbers (ASNs). Your
gateways advertise the appropriate routes (BGP prefixes) over their VPN connections.
These routing advertisements are received and readvertised to each BGP peer so that
each site can send data to and receive data from the other sites. The remote network
prefixes for each spoke must have unique ASNs, and the sites must not have
Page 11 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
overlapping IP ranges. Each site can also send and receive data from the VPC as if they
were using a standard VPN connection.
This option can be combined with AWS Direct Connect or other hardware VPN options
(e.g., multiple gateways per site for redundancy or backbone routing that you provide)
depending on your requirements.
Additional Resources
AWS VPN CloudHub 11
Amazon VPC VPN Guide
Customer Gateway device minimum requirements 12
Customer Gateway devices known to work with Amazon VPC 13
AWS Direct Connect product page 14
11
http://docs.amazonwebservices.com/AmazonVPC/latest/UserGuide/VPN_CloudHub.html
12
http://aws.amazon.com/vpc/faqs/#C8
13
http://aws.amazon.com/vpc/faqs/#C9
14
http://aws.amazon.com/directconnect/
Page 12 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Software VPN
Amazon VPC offers you the flexibility to fully manage both sides of your Amazon VPC
connectivity by creating a VPN connection between your remote network and a software
VPN appliance running in your Amazon VPC network. This option is recommended if
you must manage both ends of the VPN connection either for compliance purposes or
for leveraging gateway devices that are not currently supported by Amazon VPCs
hardware VPN solution. Figure 6 shows this option.
Clients Clients
Software VPN
Appliance
VPC Subnet 1
Internet
Availability Zone
EC2 Instances
VPC Subnet 2 Remote
Servers
Availability Zone
Customer
Amazon VPC Remote Network
You can choose from an ecosystem of multiple partners and open source communities
that have produced software VPN appliances that run on Amazon EC2. These include
products from well-known security companies like Check Point, Astaro, OpenVPN
Technologies, and Microsoft, as well as popular open source tools like OpenVPN,
Openswan, and IPsec-Tools. Along with this choice comes the responsibility for you to
manage the software appliance, including configuration, patches, and upgrades.
Note that this design introduces a potential single point of failure into the network design
as the software VPN appliance runs on a single Amazon EC2 instance. See Appendix
A: High-Level HA Architecture for Software VPN Instances for additional information.
Page 13 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Additional Resources
VPN Appliances from the AWS Marketplace 15
Tech Brief - Connecting Cisco ASA to VPC EC2 Instance (IPSec) 16
Tech Brief - Connecting Multiple VPCs with EC2 Instances (IPSec) 17
Tech Brief - Connecting Multiple VPCs with EC2 Instances (SSL) 18
15
https://aws.amazon.com/marketplace/search/results/ref=brs_navgno_search_box?searchTerms=vpn
16
http://aws.amazon.com/articles/8800869755706543
17
Although these guides specifically address connecting multiple Amazon VPCs, they are easily adaptable to
support this network configuration by substituting one of the VPCs with an on-premises VPN device connecting to
an IPsec or SSL software VPN appliance running in an Amazon VPC.
18
http://aws.amazon.com/articles/0639686206802544
Page 14 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
VPC connectivity between VPCs is best achieved when using nonoverlapping IP ranges
for each VPC being connected. For example, if youd like to connect multiple VPCs,
make sure each VPC is configured with unique Classless Inter-Domain Routing (CIDR)
ranges. Therefore, we advise you to allocate a single, contiguous, nonoverlapping CIDR
block to be used by each VPC. For additional information about Amazon VPC routing
and constraints, see the Amazon VPC Frequently Asked Questions:
http://aws.amazon.com/vpc/faqs/.
Page 15 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Hardware VPN VPC-to-VPC routing Reuse existing Amazon VPC VPN Network latency, variability,
managed by you over connections and availability depend on
hardware-based, AWS-managed endpoint includes Internet conditions
IPsec VPN multidata center redundancy and The endpoint you manage is
connections using automated failover responsible for
your equipment and implementing redundancy
Supports static routes and
the Internet and failover (if required)
dynamic BGP peering and routing
policies
AWS Direct VPC-to-VPC routing Consistent network performance May require additional
Connect managed by you Reduced bandwidth costs telecom and hosting
using your equipment provider relationships
1 or 10 Gbps provisioned
in an AWS Direct
connections
Connect location and
private lines Supports static routes and BGP
peering and routing policies
Page 16 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
VPC Peering
A VPC peering connection is a networking connection between two VPCs that enables
routing using each VPCs private IP addresses as if they were in the same network.
This is the AWS recommended method for connecting VPCs within a region. VPC
peering connections can be created between your own VPCs or with a VPC in another
AWS account within the same AWS region.
A VPC peering connection can help you to facilitate the transfer of data between VPCs.
You can use them to connect VPCs when you have more than one AWS account, to
connect a management or shared services VPC to application- or customer-specific
Page 17 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
VPCs, or to connect seamlessly with a partners VPC. For more examples of scenarios
in which you can use a VPC peering connection, see the Amazon VPC Peering Guide. 19
Additional Resources
Amazon VPC User Guide 20
Amazon VPC Peering Guide
19
http://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/
20
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-peering.html
Page 18 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Software VPN
Amazon VPC provides network routing flexibility. This includes the ability to create
secure VPN tunnels between two or more software VPN appliances to connect multiple
VPCs into a larger virtual private network so that instances in each VPC can seamlessly
connect to each other using private IP addresses. This option is recommended when
you want to connect VPCs across multiple AWS regions and manage both ends of the
VPN connection using your preferred VPN software provider. This option uses an
Internet gateway attached to each VPC to facilitate communication between the software
VPN appliances.
You can choose from an ecosystem of multiple partners and open source communities
that have produced software VPN appliances that run on Amazon EC2. These include
products from well-known security companies like Check Point, Sophos, OpenVPN
Technologies, and Microsoft, as well as popular open source tools like OpenVPN,
Openswan, and IPsec-Tools. Along with this choice comes the responsibility for you to
manage the software appliance including configuration, patches, and upgrades.
Note that this design introduces a potential single point of failure into the network design
as the software VPN appliance runs on a single Amazon EC2 instance. See Appendix
A: High-Level HA Architecture for Software VPN Instances for additional information.
Page 19 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Additional Resources
VPN Appliances from the AWS Marketplace
Tech Brief - Connecting Multiple VPCs with EC2 Instances (IPSec) 21
Tech Brief - Connecting Multiple VPCs with EC2 Instances (SSL) 22
Software-to-Hardware VPN
Amazon VPC provides the flexibility to combine the hardware VPN and software VPN
options to connect multiple VPCs. With this design, you can create secure VPN tunnels
between a software VPN appliance and a virtual private gateway to connect multiple
VPCs into a larger virtual private network, allowing instances in each VPC to seamlessly
connect to each other using private IP addresses. This option is recommended when
you want to connect VPCs across multiple AWS regions and would like to take
advantage of the AWS-managed hardware VPN endpoint including automated multidata
center redundancy and failover built into the VGW side of the VPN connection. This
option uses a virtual private gateway in one Amazon VPC and a combination of an
Internet gateway and software VPN appliance in another Amazon VPC as shown in
Figure 9.
21
http://aws.amazon.com/articles/5472675506466066
22
http://aws.amazon.com/articles/0639686206802544
Page 20 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Note that this design introduces a potential single point of failure into the network design
as the Astaro Security Gateway appliance runs on a single Amazon EC2 instance.
Please see Appendix A: High-Level HA Architecture for Software VPN Instances for
additional information.
Additional Resources
Tech Brief - Connecting Multiple VPCs with Sophos Security Gateway 23
Configuring Windows Server 2008 R2 as a Customer Gateway for Amazon Virtual
Private Cloud 24
23
http://aws.amazon.com/articles/1909971399457482
24
http://docs.amazonwebservices.com/AmazonVPC/latest/UserGuide/CustomerGateway-Windows.html
Page 21 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Hardware VPN
Amazon VPC provides the option of creating a hardware IPsec VPN to connect your
remote networks with your Amazon VPCs over the Internet. You can leverage multiple
hardware VPN connections to route traffic between your Amazon VPCs as shown in
Figure 10.
Page 22 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
We recommend this approach when you want to take advantage of AWS-managed VPN
endpoints including the automated multidata center redundancy and failover built into the
AWS side of each VPN connection. Although not shown, the Amazon VGW represents
two distinct VPN endpoints, physically located in separate data centers to increase the
availability of each VPN connection.
Amazon VGW also supports multiple customer gateway connections (as described in
the Customer NetworktoAmazon VPC Options and Hardware VPN sections and
shown in Figure 2), allowing you to implement redundancy and failover on your side of
the VPN connection. This solution can also leverage BGP peering to exchange routing
information between AWS and these remote endpoints. You can specify routing
priorities, policies, and weights (metrics) in your BGP advertisements to influence the
network path traffic will take to and from your network(s) and AWS.
This approach is suboptimal from a routing perspective since the traffic must traverse
the Internet to get to and from your network, but it gives you a lot of flexibility for
controlling and managing routing on your local and remote networks, as well as the
potential ability to reuse hardware VPN connections.
Additional Resources
Amazon VPC Users Guide
Customer Gateway device minimum requirements
Customer Gateway devices known to work with Amazon VPC
Tech Brief - Connecting a Single Router to Multiple VPCs 25
You can divide a physical AWS Direct Connect connection into multiple logical
connections, one for each VPC. You can then use these logical connections for routing
traffic between VPCs, as shown in Figure 11. In addition to intraregion routing, you can
connect AWS Direct Connect locations in other regions using your existing WAN
providers and leverage AWS Direct Connect to route traffic between regions over your
WAN backbone network.
25
http://aws.amazon.com/articles/5458758371599914
Page 23 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Page 24 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
connections physically attached to the AWS network in each region. Additionally, this
service gives you the most flexibility for controlling and managing routing on your local
and remote networks, as well as the potential ability to reuse AWS Direct Connect
connections.
Additional Resources
AWS Direct Connect product page 26
AWS Direct Connect locations 27
AWS Direct Connect FAQs 28
Get Started with AWS Direct Connect 29
26
http://aws.amazon.com/directconnect/
27
http://aws.amazon.com/directconnect/#details
28
http://aws.amazon.com/directconnect/faqs/
29
http://docs.amazonwebservices.com/DirectConnect/latest/GettingStartedGuide/Welcome.html
Page 25 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
With software remote-access VPN, you can leverage low cost, elastic, and secure
Amazon Web Services to implement remote-access solutions while also providing a
seamless experience connecting to AWS hosted resources. In addition, you can
combine software remote-access VPNs with your network-to-Amazon VPC options to
provide remote access to internal networks if desired. This option is typically preferred
by smaller companies with less extensive remote networks or who have not already built
and deployed remote access solutions for their employees.
The following table outlines the advantages and limitations of these options.
User Network-to- Virtual extension of Leverages existing end-user Requires existing end-user
Amazon VPC your data center internal and remote-access internal and remote access
Options into AWS policies and technologies implementations
Page 26 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Page 27 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
As with the software VPN options, the customer is responsible for managing the remote
access software including user management, configuration, patches and upgrades.
Additionally, please note that this design introduces a potential single point of failure into
the network design as the remote access server runs on a single Amazon EC2 instance.
Please see Appendix A: High-Level HA Architecture for Software VPN Instances for
additional information.
Additional Resources
VPN Appliances from the AWS Marketplace
OpenVPN Access Server Quick Start Guide 30
30
http://docs.openvpn.net/how-to-tutorialsguides/virtual-platforms/amazon-ec2-appliance-ami-quick-start-guide/
Page 28 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Conclusion
AWS provides a number of efficient, secure connectivity options to help you get the most
out of AWS when integrating your remote networks with Amazon VPC. The options
provided in this whitepaper highlight several of the connectivity options and patterns that
others have leveraged to successfully integrate their remote networks or multiple
Amazon VPC networks. We hope that these options will help you determine the most
appropriate mechanism for connecting the infrastructure required to run your business
regardless of where it is physically located or hosted.
Page 29 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
woute Table 1
Destination Target
VtC Local
VPN
Connection Clients Clients
Software VPN
EC2 Instances Appliance
VPC Subnet 1
Availability Zone
Internet
Internet
Vtb Gateway Customer VPN
End-Point
aonitor VPN
Connection
Software VPN
EC2 Instances
Appliance
VPC Subnet 2 Remote
Servers
Availability Zone woute Table 2
Destination Target
Customer
Amazon VPC Remote Network
VtC Local
We recommend configuring your VPC route tables to leverage all VPN instances
simultaneously by directing traffic from all of the subnets in one Availability Zone through
its respective VPN instances in the same Availability Zone. Each VPN instance will then
provide VPN connectivity for instances that share the same Availability Zone.
Page 30 of 31
Amazon Web Services Amazon VPC Connectivity Options July 2014
Page 31 of 31