AWS Direct Connect & VPN's - Pop-up Loft Tel Aviv
•
4 likes•1,733 views
As enterprises move to the cloud, robust connectivity is often an early consideration. AWS Direct Connect provides a more consistent network experience for accessing your AWS resources, typically with greater bandwidth and reduced network costs. This session dives deep into the features of AWS Direct Connect and VPNs. We discuss deployment architectures and demonstrate the process from start to finish. We’ll show you how to configure public and private virtual interfaces, configure routers, use VPN backup, and provide secure communication between sites by using the AWS VPN CloudHub.
Report
Share
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to AWS Direct Connect & VPN's - Pop-up Loft Tel Aviv
Similar to AWS Direct Connect & VPN's - Pop-up Loft Tel Aviv (20)
More from Amazon Web Services
More from Amazon Web Services (20)
Recently uploaded
Recently uploaded (20)
AWS Direct Connect & VPN's - Pop-up Loft Tel Aviv
- 1. AWS Direct Connect & VPN’s Steve Seymour Specialist Solutions Architect
- 2. Amazon VPC Availability Zone Virtual Private Cloud AWS Cloud Public Subnet Internet Virtual Private Cloud Availability Zone Private Subnet Availability Zone VPN Only Subnet Application Servers Web Server Web Server NAT Corporate Network R Database Servers
- 3. Amazon VPC
- 4. Corporate Network Internet ISP 2 (BGP) FIREWALL Internet ISP 1 Internet ISP 3 OSPF Router PublicIP Router BGP Inside GRE Tunnels Over IPSEC FIREWALL Internet ISP 4 Internet ISP 5 OSPF .1 Wireless Controller Backup GRE Tunnels Router
- 9. The Toolbox Virtual Private Cloud Route Tables Internet Gateway Virtual Private Gateway VPN Connection Customer Gateway AWS Direct Connect
- 11. Connectivity Options AWS Hardware VPN Demo AWS Direct Connect
- 12. AWS Hardware VPN
- 13. Internet Protocol Security (IPsec) is a protocol suite for securing Internet Protocol (IP) communications by authenticating and encrypting each IP packet of a communication session. IPsec includes protocols for establishing mutual authentication between agents at the beginning of the session and negotiation of cryptographic keys to be used during the session. Reference: Wikipedia - http://en.wikipedia.org/wiki/IPsec VPN Connection – IPsec
- 14. Internet Protocol Security (IPsec) is a protocol suite for securing Internet Protocol (IP) communications by authenticating and encrypting each IP packet of a communication session. IPsec includes protocols for establishing mutual authentication between agents at the beginning of the session and negotiation of cryptographic keys to be used during the session. Reference: Wikipedia - http://en.wikipedia.org/wiki/IPsec VPN Connection – IPsec
- 15. AWS VPN Features • Static or Dynamic (BGP) • Static requires routes (IP Prefixes) to be specified • Dynamic VPN supports max-prefixes of 100 • BGP over VPN supports 2-byte AS Numbers
- 16. AWS VPN Requirements • Connections initiated from the Customer Gateway • IKE Security Association using a Pre-Shared Key • IPSec Security Associations in Tunnel Mode • AES 128-bit encryption, SHA-1 hashing function • Diffie-Hellman Perfect Forward Secrecy – Group 2 • Dead Peer Detection • Fragment IP Packets before encryption
- 17. Static VPN CORP • 1 unique Security Association (SA) pair per tunnel • 1 inbound and 1 outbound • 2 unique pairs for 2 tunnels – 4 SA’s 10.0.0.0 /16 10.0.0.0 /16 192.168.0.0 /16 192.168.0.0 /16 10.0.0.0 /16
- 18. Static VPN CORP • Consolidate ACL’s to cover all IP’s • Filter to block unwanted traffic 0.0.0.0/0 (any) 0.0.0.0/0 (any) 172.16.0.0 /12 192.168.1.0 /24 192.168.9.0 /24 192.168.1.0 /24 192.168.9.0 /24 172.16.0.0 /12 10.0.0.0 /16
- 19. Static VPN CORP • Consolidate ACL’s to cover all IP’s • Filter to block unwanted traffic 10.0.0.0 /16 10.0.0.0 /16 0.0.0.0 /0 (any) 0.0.0.0 /0 (any) 10.0.0.0 /16
- 20. What is BGP ? • TCP based protocol on port 179 • BGP Neighbors exchange routing information - prefixes • More specific prefixes are preferred • Uses Autonomous System Numbers – AS Numbers • iBGP – between peers in the same AS • eBGP – between peers in different AS • AS_PATH – measure of network “distance” • Local Preference – weighting of identical prefixes
- 21. Dynamic VPN CORP Tunnel 1 IP 169.254.169.1 /30 BGP AS 7224 Route Table Destination Target 10.0.0.0/16 Local 172.16.0.0/16 VGW Tunnel 2 IP 169.254.169.5 /30 BGP AS 7224 10.0.0.0 /16 Tunnel 1 IP 169.254.169.2 /30 BGP AS 65001 Tunnel 2 IP 169.254.169.6 /30 BGP AS 65001 172.16.0.0 /16
- 22. Dynamic VPN CORP Tunnel 1 IP 169.254.169.1 /30 BGP AS 17493 Tunnel 2 IP 169.254.169.5 /30 BGP AS 17493 10.0.0.0 /16 Tunnel 1 IP 169.254.169.2 /30 BGP AS 65001 Tunnel 2 IP 169.254.169.6 /30 BGP AS 65001 172.16.0.0 /16 • BGP Peer IP Addresses are automatically generated • Customer AS Number – owned or private ASN • Amazon AS Number is fixed per region
- 23. Path Selection – inside the VGW 1. Most specific IP prefix 192.168.10.0/24 over 192.168.0.0/16 2. Direct Connect (irrelevant of AS PATH length) 3. Static VPN Connection 4. Dynamic (BGP) VPN Connection 4. Shortest AS PATH 65001 i over 65001 65001 i
- 25. Resilient Dynamic VPN – Multiple VPC’s CORP
- 26. Recent VPN Updates • NAT Traversal (NAT-T) • Re-usable Customer Gateway • Allows for the same Customer Gateway (CGW) IP • Create a new VGW and VPN then attach to your VPC Note: Only one VGW can be attached to a VPC at one time. • Additional Encryption Options • AES256, SHA-256 • Phase 1 can now use DH groups 2, 14-18, 22, 23, and 24. • Phase 2 can now use DH groups 1, 2, 5, 14-18, 22, 23, and 24.
- 27. How to Create a VPN Connection 1. Create a VGW 2. Attach it to the VPC 3. Create a CGW 4. Create a VPN 5. Update Route Tables 6. Configure CGW
- 28. How to Create a VPN Connection 1. Create a VGW 2. Attach it to the VPC 3. Create a CGW 4. Create a VPN 5. Update Route Tables 6. Configure CGW
- 29. How to Create a VPN Connection 1. Create a VGW 2. Attach it to the VPC 3. Create a CGW 4. Create a VPN 5. Update Route Tables 6. Configure CGW
- 30. How to Create a VPN Connection 1. Create a VGW 2. Attach it to the VPC 3. Create a CGW 4. Create a VPN 5. Update Route Tables 6. Configure CGW
- 31. How to Create a VPN Connection 1. Create a VGW 2. Attach it to the VPC 3. Create a CGW 4. Create a VPN 5. Update Route Tables 6. Configure CGW
- 32. How to Create a VPN Connection 1. Create a VGW 2. Attach it to the VPC 3. Create a CGW 4. Create a VPN 5. Update Route Tables 6. Configure CGW
- 34. What is AWS Direct Connect… Dedicated, private pipes into AWS Create private (VPC) or public virtual interfaces to AWS Reduced data-out rates (data-in still free)) Consistent network performance At least 1 location to each AWS region Option for redundant connections Multiple AWS accounts can share a connection Inter-Region enables connectivity to multiple regions in US Uses BGP to exchange routing information over a VLAN
- 35. Direct Connect - Locations AWS Region AWS Direct ConnectLocation Asia Pacific (Seoul) KINX, Seoul, Korea Asia Pacific (Singapore) Equinix SG2, Singapore Asia Pacific (Singapore) GPX, Mumbai, India Asia Pacific (Sydney) Equinix SY3, Sydney, Australia Asia Pacific (Sydney) Global Switch, Sydney, Australia Asia Pacific (Tokyo) Equinix OS1, Osaka, Japan Asia Pacific (Tokyo) Equinix TY2, Tokyo, Japan AWS GovCloud (US) Equinix SV1 & SV5, San Francisco, CA China (Beijing) CIDS Jiachuang IDC, Beijing, China China (Beijing) Sinnet Jiuxianqiao IDC, Beijing, China EU Central (Frankfurt) Equinix FR5, Frankfurt, Germany EU Central (Frankfurt) Interxion Frankfurt, Germany EU West (Ireland) Equinix LD4 - LD6, London, England EU West (Ireland) Eircom Clonshaugh, Dublin, Ireland EU West (Ireland) TelecityGroup, London Docklands', London, England South America (Sao Paulo) Terremark NAP do Brasil, Sao Paulo, Brasil South America (Sao Paulo) Tivit, Sao Paulo, Brasil US East (Virginia) CoreSite NY1 & NY2, New York, NY US East (Virginia) Equinix DA1 - DA3 & DA6, Dallas, TX US East (Virginia) Equinix DC1 - DC6 & DC10, Ashburn, VA US West (Northern California) CoreSite One Wilshire & 900 North Alameda, CA US West (Northern California) Equinix SV1 & SV5, San Francisco, CA US West (Oregon) Equinix SE2 & SE3, Seattle, WA US West (Oregon) Switch SUPERNAP 8, Las Vegas, NV
- 36. Layers of Direct Connect Single Mode Fiber – 1G or 10GLayer 1 - Physical Ethernet – 802.1Q VLANLayer 2 – Data Link Peer & Amazon IPLayer 3 - Network TCPLayer 4 - Transport BGPLayer 7 - Application “Routing of traffic”
- 37. Terminology For Physical Connections Leased Line Ethernet Private Line Pseudo-wire Point-to-point circuit LAN Extension MPLS / VPLS / IP-VPN / L3-VPN
- 38. Terminology For Physical Connections Leased Line Ethernet Private Line Pseudo-wire Point-to-point circuit LAN Extension MPLS / VPLS / IP-VPN / L3-VPN All generally deliver an “extension” of a port from a Direct Connect Location to a Customer Location}
- 39. Leased Line Ethernet Private Line Pseudo-wire Point-to-point circuit LAN Extension MPLS / VPLS / IP-VPN / L3-VPN Terminology For Physical Connections A little different …}
- 40. Physical Connection • Cross Connect at the location • Single Mode Fiber - 1000Base-LX or 10GBASE-LR • Potential onward Delivery via Direct Connect Partner • Customer Router
- 41. At the Direct Connect Location CORP AWS Direct Connect Routers Customer Router Colocation DX Location Customer Network ` AWS Backbone Network Cross Connect Customer Router Access Circuit Customers Network Backbone Access Circuit Demarcation
- 42. Dedicated Port via Direct Connect Partner CORP AWS Direct Connect Routers Colocation DX Location Partner Network AWS Backbone Network Cross Connect Customer Router Partner Network Access Circuit Demarcation Partner Equipment
- 43. At the Direct Connect Location – via MPLS CORP AWS Direct Connect Routers Partner PE Router Colocation DX Location MPLS Core ` AWS Backbone Network Cross Connect Provider Edge Partner MPLS Core Access Circuit to CE Demarcation ` ` CE Router CE Router
- 44. Layers of Direct Connect Direct Connect Connection Ethernet – 802.1Q VLAN Peer & Amazon IP Virtual Interface (One per VLAN) BGP Virtual Private Gateway A/C 1 “Routing of traffic” Single Mode Fiber – 1G or 10G
- 45. Public and Private Virtual Interfaces • 802.1Q VLAN • eBGP Session Note: Max Prefixes on the AWS peer : 100 • Private Virtual Interface – Access to VPC Note: Not VPC Endpoints or transitive via VPC Peering • Public Virtual Interface – Access to non-VPC Services
- 46. Account ownership of Direct Connect Direct Connect Connection Ethernet – 802.1Q VLAN Peer & Amazon IP Hosted Virtual Interface (One per VLAN) BGP Virtual Private Gateway A/C 1 A/C 2 “Routing of traffic” Single Mode Fiber – 1G or 10G
- 47. Sub-1G via Direct Connect Partner Direct Connect Interconnect Ethernet – 802.1Q VLAN Hosted Connection Virtual Interface (Single) BGP Virtual Private Gateway PartnerCustomer Bandwidth VLAN Peer & Amazon IP’s “Routing of traffic” Single Mode Fiber – 1G or 10G 50Mbps, 100Mbps, 200Mbps, 300Mbps, 400Mbps and 500Mbps
- 48. Sharing Hosted Connections Direct Connect Interconnect Ethernet – 802.1Q VLAN Hosted Connection Hosted Virtual Interface (Single) BGP Virtual Private Gateway PartnerCustomerA/C2 Bandwidth VLAN Peer & Amazon IP’s A/C 1 “Routing of traffic” Single Mode Fiber – 1G or 10G
- 49. Private Virtual Interface • Only provides access to resources in a VPC Note: Not VPC Endpoints or transitive via VPC Peering • Attaches to the Virtual Private Gateway Same as a VPN Connection • Multiple Private VIF’s can be attached for resilience • Any IP Addresses and ASN for BGP Peering acceptable
- 50. Single Private Virtual Interface CORP Route Table Destination Target Propagated 10.0.0.0/16 Local 172.16.0.0/16 VGW Yes 10.0.0.0 /16 172.16.0.0 /16 dxvif-wwxxyyzz VLAN 100 IP 169.254.254.9 /30 BGP AS 7224 MD5 Key Interface gi0/0.100 VLAN 100 IP 169.254.254.10 /30 BGP AS 65001 MD5 Key eBGP AS65001 Announcing 172.16.0.0 /16 AS7224 Announcing 10.0.0.0 /16
- 51. Dual DX – Single Location CORP AWS Direct Connect Routers Customer Router Colocation DX Location Service Provider Network `
- 52. eBGP eBGP Dual Private Virtual Interface CORP 10.0.0.0 /16 172.16.0.0 /16 dxvif-wwxxyyzz VLAN 100 IP 169.254.254.9 /30 BGP AS 7224 MD5 Key Interface gi0/0.100 VLAN 100 IP 169.254.254.10 /30 BGP AS 65001 MD5 Key dxvif-aabbccdd VLAN 100 IP 169.254.254.13 /30 BGP AS 7224 MD5 Key Interface gi0/0.100 VLAN 100 IP 169.254.254.14 /30 BGP AS 65001 MD5 Key
- 53. eBGP eBGP Dual Private Virtual Interface CORP 10.0.0.0 /16 172.16.0.0 /16 dxvif-wwxxyyzz VLAN 100 IP 169.254.254.9 /30 BGP AS 7224 MD5 Key Interface gi0/0.100 VLAN 100 IP 169.254.254.10 /30 BGP AS 65001 MD5 Key dxvif-aabbccdd VLAN 100 IP 169.254.254.13 /30 BGP AS 7224 MD5 Key Interface gi0/0.100 VLAN 100 IP 169.254.254.14 /30 BGP AS 65001 MD5 Key
- 54. Dual DX – Single Location revisited CORP AWS Direct Connect Routers Customer Router Colocation DX Location Service Provider Network `
- 55. Dual DX – Single Location revisited CORP AWS Direct Connect Routers Customer Routers Colocation DX Location ` Service Provider Network `
- 56. Single DX – Dual Location CORP Customer Routers Colocation DX Location 1 ` Customer Routers Colocation DX Location 2 ` Service Provider Network AWS Direct Connect Routers AWS Direct Connect Routers
- 57. Dual DX – Dual Location CORP AWS Direct Connect Routers Customer Routers Colocation DX Location 1 ` ` AWS Direct Connect Routers Customer Routers Colocation DX Location 2 ` ` Service Provider Network
- 58. Dual VIF – Active/Active IP 169.254.254.9 /30 IP 169.254.254.13 /30
- 59. Active/Active – the VGW Perspective IP 169.254.254.10 /30 IP 169.254.254.14 /30
- 60. Dual VIF – Active/Passive IP 169.254.254.9 /30 IP 169.254.254.13 /30
- 61. Active/Passive – the VGW Perspective IP 169.254.254.10 /30 IP 169.254.254.14 /30
- 62. Dual VIF – Active/Passive IP 169.254.254.9 /30 IP 169.254.254.13 /30
- 63. Active/Passive – the VGW Perspective IP 169.254.254.10 /30 IP 169.254.254.14 /30
- 64. Public Virtual Interface • Provides access to Amazon Public IP Addresses • Requires Public IP Addresses for BGP Session If you can’t provide them, raise a case with AWS Support • Public ASN must be owned by customer – Private is OK • Inter-Region is available in the US
- 65. Public VIF – Inter-Region – US Only Public VIF’s receive prefixes for all US Regions Prefixes are identified by BGP Communities Advertisements can be controlled via BGP Communities
- 66. Public Virtual Interface CORP 172.16.0.0 /16 dxvif-wwxxyyzz VLAN 200 IP 54.239.244.57 /31 BGP AS 7224 MD5 Key Interface gi0/0.200 VLAN 200 IP 54.239.244.56 /31 BGP AS 65001 MD5 Key AS65001 Announcing 54.239.244.56 /31 AS7224 Announcing 184.72.96.0/19 via 7224 16509 14618 i 184.72.128.0/17 via 7224 16509 14618 i 184.73.0.0 via 7224 16509 14618 i 184.169.128.0/17 via 7224 16509 i 199.127.232.0/22 via 7224 16509 i 199.255.192.0/22 via 7224 16509 I …... …..
- 67. Public Virtual Interface IP 54.239.244.57 /31 BGP AS 7224
- 68. Public Virtual Interface IP 54.239.244.57 /31 BGP AS 7224
- 69. Ordering Process
- 70. How to order AWS Direct Connect 1. Select Your Region 2. Create a Connection 3. Receive LOA-CFA 4. Cross Connect 5. Create Virtual Interface 6. Configure Customer Router
- 71. How to order AWS Direct Connect 1. Select Your Region 2. Create a Connection 3. Receive LOA-CFA 4. Cross Connect 5. Create Virtual Interface 6. Configure Customer Router
- 72. How to order AWS Direct Connect 1. Select Your Region 2. Create a Connection 3. Receive LOA-CFA 4. Cross Connect 5. Create Virtual Interface 6. Configure Customer Router
- 73. How to order AWS Direct Connect 1. Select Your Region 2. Create a Connection 3. Receive LOA-CFA 4. Cross Connect 5. Create Virtual Interface 6. Configure Customer Router
- 74. How to order AWS Direct Connect 1. Select Your Region 2. Create a Connection 3. Receive LOA-CFA 4. Cross Connect 5. Create Virtual Interface 6. Configure Customer Router
- 75. How to order AWS Direct Connect 1. Select Your Region 2. Create a Connection 3. Receive LOA-CFA 4. Cross Connect 5. Create Virtual Interface 6. Configure Customer Router
- 76. How to order sub-1G via an APN Partner 1. Provide your Direct Connect Partner with Account Number 2. Accept Hosted Connection 3. Create Virtual Interface 4. Configure Customer Router
- 77. How to order sub-1G via an APN Partner 1. Provide your Direct Connect Partner with Account Number 2. Accept Hosted Connection 3. Create Virtual Interface 4. Configure Customer Router
- 78. How to order sub-1G via an APN Partner 1. Provide your Direct Connect Partner with Account Number 2. Accept Hosted Connection 3. Create Virtual Interface 4. Configure Customer Router
- 79. How to order sub-1G via an APN Partner 1. Provide your Direct Connect Partner with Account Number 2. Accept Hosted Connection 3. Create Virtual Interface 4. Configure Customer Router
- 80. Direct Connect with VPN Backup CORP DX Location 1 DX Location 2
- 81. Hardware VPN over DX Public VIF CORP 172.16.0.0 /16 dxvif-wwxxyyzz VLAN 200 IP 54.239.244.57 /31 BGP AS 7224 MD5 Key Interface gi0/0.200 VLAN 200 IP 54.239.244.56 /31 BGP AS 65001 MD5 Key Tunnel 1 IP 169.254.169.1 /30 BGP AS 17493 Tunnel 2 IP 169.254.169.5 /30 BGP AS 17493 Tunnel 1 IP 169.254.169.2 /30 BGP AS 65001 Tunnel 2 IP 169.254.169.6 /30 BGP AS 65001
- 82. Billing • VPN Connections Connection Hours Data Transfer (Internet rates) • Direct Connect Port Hours Reduced Data Transfer Rates No charge for resources owned by other accounts VPN Data Transfer over Direct Connect at reduced rate
- 83. Things to remember All Direct Connect locations are at 3rd party data centers You will have to work with at least one other organization • Could be just the Data Center • Could be a Network Provider / Direct Connect Partner • Could be multiple Network Providers AND the Data Center Sub-1G Hosted Connections support a single VIF You can share VIF’s with other accounts Public VIF’s include the Hardware VPN Endpoints
- 85. Demo
- 86. Demo Architecture 192.168.51.0 /24 192.168.51.10 Gi0/1: 192.168.51.254 Gi0/0 Internet Gi0/0/0 DX 1 DX Location (Telecity London) eu-west-1 (Ireland) 10.0.0.0 /16
- 87. Summary Connectivity via VPN – Static & Dynamic Connectivity via AWS Direct Connect – Public & Private Demo
- 88. Steve Seymour Specialist Solutions Architect seymours@amazon.co.uk @sseymour