1. Home
  2. Training Library
  3. Amazon Web Services
  4. Courses
  5. AWS Virtual Private Cloud: Subnets and Routing

Routing: VPC Endpoints

The course is part of these learning paths

Security - Specialty Certification Preparation for AWS
24
2
12
4
AWS Networking & Content Delivery
15
2
9
AWS Advanced Networking – Specialty Certification Preparation
19
2
8
4
more_horizSee 1 more
Start course
Overview
Difficulty
Advanced
Duration
1h 19m
Students
6884
Ratings
4.7/5
starstarstarstarstar-half
Description

Creating and configuring a Virtual Private Cloud (VPC) within AWS can be a simple or difficult process. It all very much depends on the complexity of your requirements. For example, how many subnets and hosts will you require? Will you be using one VPC or peering multiple VPCs together? Do you need to establish connectivity back to your on-premise network? Do you need internet connectivity for your Private instances? These and many more questions need to be asked and answered before you start to design your VPC infrastructure.

As a part of this process, you will need to understand VPC Subnet configurations and VPC routing to ensure you architect your solution correctly and efficiently.

This AWS Virtual Private Cloud: Subnets and Routing course looks and VPC Subnets and VPC Routing in detail, providing examples of both across different configurations and solutions and how to best implement your network design.

Course lectures

VPC Subnets:

  • VPC CIDR Blocks - This lecture focuses on the effect of subnetting your VPC CIDR Block
  • Why Subnet your VPC - This lecture looks at some of the reasons why you may want to subnet your VPC, by looking at the advantages and benefits
  • VPC Subnets - This lecture dives into at what a VPC Subnet looks like within the Management Console and its associated components such as Network Access Control Lists (NACLs)
  • Public & Private Subnets - This lecture looks at the differences between both Public and Private subnets within a VPC
  • VPC Peering: Subnet Considerations - This lecture focuses on some of the considerations when architecting your subnets in different VPC Peering configurations
  • Flow Logs: VPC Subnets - This lecture dives into at what a VPC Subnet looks like within the Management Console and its associated components such as Network Access Control Lists (NACLs)
  • Demonstration: Creating a VPC & Subnets - This lecture provides a demonstration on how to set up and configure a VPC with both Public and Private subnets

VPC Routing:

  • Routing Fundamentals & Route Tables - This lecture introduces AWS routing and its Routing tables by breaking down all the components within it
  • Routing Priorities - This lecture explains how the routing priorities are defined for overlapping routes within the same route table
  • Routing: VPC Peering - This lecture looks are different routing configurations for multiple VPC peering scenarios
  • Routing: VPN Connection via a Virtual Private Gateway - This lecture looks at routing configurations for virtual Private Gateways
  • Routing: Internet Gateways & NAT Gateways - This lecture looks at the routing configurations for both IGWs and NAT Gateways and the dependencies involved
  • Routing: VPC Endpoints - This lecture looks at the automatic routing configuration when creating a VPC Endpoint
Transcript

Hello, and welcome to this lecture on the final routing configuration scenarios using VPC endpoints. A VPC endpoint is a virtual device which allows you to connect your VPC to another AWS service without traversing any gateway of any kind, such as an internet Gateway, a virtual gateway or a NAT gateway.

Currently, the only supported endpoint is for S3, and when using these endpoints it doesn't impose risks of availability or bandwidth across your VPC network, as it uses horizontally scaled, highly available VPC components, which are all held on the AWS network. When communicating between the VPC endpoint and your VPC, the traffic remains inside the global AWS network.

So how is this routing managed between your VPC subnet and these VPC endpoints? Well, the routing is implemented automatically. To create a VPC endpoint, select "Endpoints" from the VPC dashboard. Then select "Create endpoint" Then select your VPC, service endpoint and access policy for the service. Then select "Next step."

At this point, in step two, "Configure Route Tables" you must select which route tables will be used to route the AWS service, which in this case, is S3. It will add a new rule for the new destination, with a target of the VPC ID. I shall create the endpoint in this example by selecting the main route table to see which route to add.

To complete setup, select "Create endpoint" As you can see, by completing the configuration of the VPC endpoint, it has automatically added a new route to the main route table, which I had selected in the previous section. The destination values and target values have automatically been added. That now brings us to the end of this lecture covering AWS routing across VPC endpoints.

Coming up next, we shall summarize what we have learnt throughout each of the previous lectures.

About the Author
Avatar
Stuart Scott
AWS Content Director
Students
168646
Labs
1
Courses
139
Learning Paths
94

Stuart has been working within the IT industry for two decades covering a huge range of topic areas and technologies, from data center and network infrastructure design, to cloud architecture and implementation.

To date, Stuart has created 90+ courses relating to Cloud reaching over 140,000 students, mostly within the AWS category and with a heavy focus on security and compliance.

Stuart is a member of the AWS Community Builders Program for his contributions towards AWS.

He is AWS certified and accredited in addition to being a published author covering topics across the AWS landscape.

In January 2016 Stuart was awarded ‘Expert of the Year Award 2015’ from Experts Exchange for his knowledge share within cloud services to the community.

Stuart enjoys writing about cloud technologies and you will find many of his articles within our blog pages.