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.
- 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
- 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
Hello, and welcome to this short lecture on Virtual Private Gateway routing for VPN connectivity.
The AWS side of the routing configuration for a VPN connection over a Virtual Private Gateway is a little less complicated than that of VPC Peering.
Before you can set up a route for a VPN over a Virtual Private Gateway, you need to create and attach a Virtual Gateway to your VPC.
These Virtual Gateways are used to help create a VPN connection between your VPC and your corporate network outside of AWS. There are many more points of configuration in setting up a VPN connection, which is outside the scope of this course. However, to simply configure the AWS routing, at this stage, all you require is the Virtual Gateway to be attached to your VPC.
Once your Virtual Gateway is created and added to your VPC, you can then update the route tables for any subnets that intend to route to your corporate date center network. However, to simply configure the AWS routing, at this stage, all you require is the Virtual Gateway to be attached to your VPC. Once your Virtual Gateway is created and added to your VPC you can then update the route tables for any subnets that intend to route to your corporate data center network.
In this diagram, we can see that an AWS subnet, 10.0.2.0/24, has two static routes in its route table pointing to the two 172.16 subnets, which are located within the corporate data center outside of AWS. The destination networks have been added with a target pointing to the Virtual Gateway, listed as vgw1234abcd.
Any traffic destined for this network will then be directed to use this Virtual Gateway. You may remember from earlier, when I spoke about route propagation and the fact that it can be enabled when you have a Virtual Gateway attached to your VPC, by enabling propagation on this Virtual Private Gateway it will include the routes used in your VPN connection.
If you do not include propagation routing for your Virtual Gateway you will need to add static routes for all network used by the VPN connection that you want to route to, which is the case in this diagram. One point to mention is that AWS does not currently support IPv6 traffic across a VPN connection.
That brings us to the end of this short lecture, next up Routing for Internet Gateways and NAT Gateways.
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 150+ courses relating to Cloud reaching over 180,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.