VPC Endpoint for Amazon S3: Simple Connectivity From AWS

Let’s discuss VPC Endpoint’s value, common use cases, and how to get it up and running with the AWS CLI.

Last month Amazon Web Services introduced VPC Endpoint for Amazon S3. In this article, I am going to explain exactly what this means, how it will change – and improve – the way AWS resources communicate with each other, and how you can get it running with the AWS CLI.

Not that it’s quite complete yet, mind you:

Currently, we support endpoints for connections with Amazon S3 within the same region only. We’ll add support for other AWS services later.

Accessing S3 the old way (without VPC Endpoint)

Traditionally, when creating a VPC with a private subnet you would set up security groups and access control lists (ACLs) to control inbound and outbound traffic. Because this is a private subnet, by default it has no access to any outside public resources. Consequently, should you need access to an outside resource, you would need to set up an Internet Gateway and route traffic through a NAT instance.

So, for example, if your EC2 instance runs an application that needs access to a file stored in an S3 bucket, before VPC Endpoint, this illustrates the only way it could be done:

VPC Endpoint: A private subnet with the main route table set up
A private subnet with the main route table set up

Accessing S3 with VPC Endpoint

Now, however, accessing S3 resources from within a private VPC subnet is much simpler. There’s no longer any need to configure a gateway or NAT instances. And as an added bonus, these endpoints are easy to set up, highly reliable, and provide a secure connection to S3.

VPC Endpoint for Amazon S3
With VPC Endpoint for Amazon S3, accessing buckets is a much simpler process

If you’d prefer to work with the console to create a VPC Endpoint, you can easily follow the clear directions from the official AWS Blog. However, I am going to show you how to do it using the AWS CLI.  (By the way, Cloud Academy has a great course guiding you through the AWS CLI if you could use some help).

Creating and Using VPC Endpoints with the AWS CLI

When we create our VPC endpoint we will use the following commands

  1. describe-route-tables (Get our VPC Id and route table for the endpoint)
  2. create-vpc-endpoint (Create your VPC endpoint)
  3. describe-vpc-endpoints (List your VPC endpoint)
  4. delete-vpc-endpoints (Delete a VPC endpoint)

So first, get our VPC ID and route table ID to use for the endpoint

$ aws ec2 describe-route-tables

Your output should look something like this:

--------------------------------------------------------------------------------------------------------
|                                          DescribeRouteTables                                         |
+------------------------------------------------------------------------------------------------------+
||                                             RouteTables                                            ||
|+-------------------------------------------------+--------------------------------------------------+|
||  RouteTableId                                   |  rtb-0404a561                                    ||
||  VpcId                                          |  vpc-731e0711                                    ||
|+-------------------------------------------------+--------------------------------------------------+|
|||                                           Associations                                           |||
||+------------------------------------------------------+-------------------------------------------+||
|||  Main                                                |  False                                    |||
|||  RouteTableAssociationId                             |  rtbassoc-a4339dc1                        |||
|||  RouteTableId                                        |  rtb-0404a561                             |||
|||  SubnetId                                            |  subnet-fcbb5b99                          |||
||+------------------------------------------------------+-------------------------------------------+||
|||                                              Routes                                              |||
||+-----------------------------------------------------+--------------------------------------------+||
|||  DestinationCidrBlock                               |  172.31.0.0/16                             |||
|||  GatewayId                                          |  local                                     |||
|||  Origin                                             |  CreateRouteTable                          |||
|||  State                                              |  active                                    |||
||+-----------------------------------------------------+--------------------------------------------+||
|||                                               Tags                                               |||
||+---------------------------------+----------------------------------------------------------------+||
|||  Key                            |  Name                                                          |||
|||  Value                          |  endpointroute                                                 |||
||+---------------------------------+----------------------------------------------------------------+||
||                                             RouteTables                                            ||
|+-------------------------------------------------+--------------------------------------------------+|
||  RouteTableId                                   |  rtb-b1849cd3                                    ||
||  VpcId                                          |  vpc-731e0711                                    ||
|+-------------------------------------------------+--------------------------------------------------+|
|||                                           Associations                                           |||
||+------------------------------------------------------+-------------------------------------------+||
|||  Main                                                |  True                                     |||
|||  RouteTableAssociationId                             |  rtbassoc-9f0f14fd                        |||
|||  RouteTableId                                        |  rtb-b1849cd3                             |||
||+------------------------------------------------------+-------------------------------------------+||
|||                                              Routes                                              |||
||+----------------------+---------------------------+----------------+-------------------+----------+||
||| DestinationCidrBlock |  DestinationPrefixListId  |   GatewayId    |      Origin       |  State   |||
||+----------------------+---------------------------+----------------+-------------------+----------+||
|||  172.31.0.0/16       |                           |  local         |  CreateRouteTable |  active  |||
|||  0.0.0.0/0           |                           |  igw-1b312779  |  CreateRoute      |  active  |||
|||                      |  pl-6ca54005              |  vpce-d7b652be |  CreateRoute      |  active  |||
||+----------------------+---------------------------+----------------+-------------------+----------+||

This tells me that my VPC ID is vpc-731e0711, and my Route Table Id  (the one connected to a subnet) is rtb-0404a561.
Now let’s create a VPC endpoint. Remember that AWS currently supports endpoints within a single region, so we should note that my default region is  ap-southeast-2.

$ aws ec2 create-vpc-endpoint --vpc-id vpc-731e0711 --service-name com.amazonaws.ap-southeast-2.s3 --route-table-ids rtb-0404a561

Here’s my output:

-------------------------------------------------------------------------------------------------------------------------------------------
|                                                            CreateVpcEndpoint                                                            |
+-----------------------------------------------------------------------------------------------------------------------------------------+
||                                                              VpcEndpoint                                                              ||
|+-------------------+-------------------------------------------------------------------------------------------------------------------+|
||  CreationTimestamp|  2015-06-04T02:45:52Z                                                                                             ||
||  PolicyDocument   |  {"Version":"2008-10-17","Statement":[{"Sid":"","Effect":"Allow","Principal":"*","Action":"*","Resource":"*"}]}   ||
||  ServiceName      |  com.amazonaws.ap-southeast-2.s3                                                                                  ||
||  State            |  available                                                                                                        ||
||  VpcEndpointId    |  vpce-97b652fe                                                                                                    ||
||  VpcId            |  vpc-731e0711                                                                                                     ||
|+-------------------+-------------------------------------------------------------------------------------------------------------------+|
|||                                                            RouteTableIds                                                            |||
||+-------------------------------------------------------------------------------------------------------------------------------------+||
|||  rtb-0404a561                                                                                                                       |||
||+-------------------------------------------------------------------------------------------------------------------------------------+||

You should now have a VpcEndpoint connecting your VPC to an Amazon S3 service in the region you chose. You can now list your VpcEndpoint and the output should be similar to what you got above – unless you created more than one VpcEndpoint:

$ aws ec2 describe-vpc-endpoints

Finally, if you don’t plan on using this again, you can delete the VpcEndpoint using the following:

$ aws ec2 delete-vpc-endpoints --vpc-endpoint-ids vpce-97b652fe

What does all this now mean?

Even once you create a VPC Endpoint, the S3 public endpoints and DNS names will continue to work as they always have. All that the EndPoint does is add a new way by which the requests are routed from your private subnet to S3. Remember also that endpoints are virtual devices: they are horizontally scaled, redundant, and highly available VPC components that allow low-risk communication between instances in your VPC and AWS services.

What an endpoint effectively does is enable instances in your VPC to use their private IP addresses to communicate with resources in other services. Consequently, your instances do not require public IP addresses, and you do not need an Internet Gateway, a NAT instance, or a virtual private gateway in your VPC. This is because you use endpoint policies to control access to resources in other services. Traffic between your VPC and the AWS service does not leave the Amazon network.

Best of all, there is no additional charge for using endpoints. You will, of course, be charged standard charges for data transfer and resource use.

Avatar

Written by

Michael Sheehy

I have been UNIX/Linux System Administrator for the past 15 years and am slowly moving those skills into the AWS Cloud arena. I am passionate about AWS and Cloud Technologies and the exciting future that it promises to bring.


Related Posts

Patrick Navarro
Patrick Navarro
— January 22, 2020

Top 5 AWS Salary Report Findings

At the speed the cloud tech space is developing, it can be hard to keep track of everything that’s happening within the AWS ecosystem. Advances in technology prompt smarter functionality and innovative new products, which in turn give rise to new job roles that have a ripple effect on t...

Read more
  • AWS
  • salary
Alisha Reyes
Alisha Reyes
— January 6, 2020

New on Cloud Academy: Red Hat, Agile, OWASP Labs, Amazon SageMaker Lab, Linux Command Line Lab, SQL, Git Labs, Scrum Master, Azure Architects Lab, and Much More

Happy New Year! We hope you're ready to kick your training in overdrive in 2020 because we have a ton of new content for you. Not only do we have a bunch of new courses, hands-on labs, and lab challenges on AWS, Azure, and Google Cloud, but we also have three new courses on Red Hat, th...

Read more
  • agile
  • AWS
  • Azure
  • Google Cloud Platform
  • Linux
  • OWASP
  • programming
  • red hat
  • scrum
Alisha Reyes
Alisha Reyes
— December 24, 2019

Cloud Academy’s Blog Digest: Azure Best Practices, 6 Reasons You Should Get AWS Certified, Google Cloud Certification Prep, and more

Happy Holidays from Cloud Academy We hope you have a wonderful holiday season filled with family, friends, and plenty of food. Here at Cloud Academy, we are thankful for our amazing customer like you.  Since this time of year can be stressful, we’re sharing a few of our latest article...

Read more
  • AWS
  • azure best practices
  • blog digest
  • Cloud Academy
  • Google Cloud
Avatar
Guy Hummel
— December 12, 2019

Google Cloud Platform Certification: Preparation and Prerequisites

Google Cloud Platform (GCP) has evolved from being a niche player to a serious competitor to Amazon Web Services and Microsoft Azure. In 2019, research firm Gartner placed Google in the Leaders quadrant in its Magic Quadrant for Cloud Infrastructure as a Service for the second consecuti...

Read more
  • AWS
  • Azure
  • Google Cloud Platform
Alisha Reyes
Alisha Reyes
— December 10, 2019

New Lab Challenges: Push Your Skills to the Next Level

Build hands-on experience using real accounts on AWS, Azure, Google Cloud Platform, and more Meaningful cloud skills require more than book knowledge. Hands-on experience is required to translate knowledge into real-world results. We see this time and time again in studies about how pe...

Read more
  • AWS
  • Azure
  • Google Cloud
  • hands-on
  • labs
Alisha Reyes
Alisha Reyes
— December 5, 2019

New on Cloud Academy: AWS Solution Architect Lab Challenge, Azure Hands-on Labs, Foundation Certificate in Cyber Security, and Much More

Now that Thanksgiving is over and the craziness of Black Friday has died down, it's now time for the busiest season of the year. Whether you're a last-minute shopper or you already have your shopping done, the holidays bring so much more excitement than any other time of year. Since our...

Read more
  • AWS
  • AWS solution architect
  • AZ-203
  • Azure
  • cyber security
  • FCCS
  • Foundation Certificate in Cyber Security
  • Google Cloud Platform
  • Kubernetes
Avatar
Cloud Academy Team
— December 4, 2019

Understanding Enterprise Cloud Migration

What is enterprise cloud migration? Cloud migration is about moving your data, applications, and even infrastructure from your on-premises computers or infrastructure to a virtual pool of on-demand, shared resources that offer compute, storage, and network services at scale. Why d...

Read more
  • AWS
  • Azure
  • Data Migration
Wendy Dessler
Wendy Dessler
— November 27, 2019

6 Reasons Why You Should Get an AWS Certification This Year

In the past decade, the rise of cloud computing has been undeniable. Businesses of all sizes are moving their infrastructure and applications to the cloud. This is partly because the cloud allows businesses and their employees to access important information from just about anywhere. ...

Read more
  • AWS
  • Certifications
  • certified
Avatar
Andrea Colangelo
— November 26, 2019

AWS Regions and Availability Zones: The Simplest Explanation You Will Ever Find Around

The basics of AWS Regions and Availability Zones We’re going to treat this article as a sort of AWS 101 — it’ll be a quick primer on AWS Regions and Availability Zones that will be useful for understanding the basics of how AWS infrastructure is organized. We’ll define each section,...

Read more
  • AWS
Avatar
Dzenan Dzevlan
— November 20, 2019

Application Load Balancer vs. Classic Load Balancer

What is an Elastic Load Balancer? This post covers basics of what an Elastic Load Balancer is, and two of its examples: Application Load Balancers and Classic Load Balancers. For additional information — including a comparison that explains Network Load Balancers — check out our post o...

Read more
  • ALB
  • Application Load Balancer
  • AWS
  • Elastic Load Balancer
  • ELB
Albert Qian
Albert Qian
— November 13, 2019

Advantages and Disadvantages of Microservices Architecture

What are microservices? Let's start our discussion by setting a foundation of what microservices are. Microservices are a way of breaking large software projects into loosely coupled modules, which communicate with each other through simple Application Programming Interfaces (APIs). ...

Read more
  • AWS
  • Docker
  • Kubernetes
  • Microservices
Nisar Ahmad
Nisar Ahmad
— November 12, 2019

Kubernetes Services: AWS vs. Azure vs. Google Cloud

Kubernetes is a popular open-source container orchestration platform that allows us to deploy and manage multi-container applications at scale. Businesses are rapidly adopting this revolutionary technology to modernize their applications. Cloud service providers — such as Amazon Web Ser...

Read more
  • AWS
  • Azure
  • Google Cloud
  • Kubernetes