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.