AWS VPC Endpoints Architecture
AWS VPC endpoints provides a secure and private communication between the resources within the Amzon VPC and AWS Services without having the requirement of Internet access. They comes with consisting interface endpoints for the AWS services through the services can be accessed through the private links and gateway endpoints for Amazon S3 and DynamoDB. It uses Elastic Network Interfaces (ENIs) for connectivity. Through its architecture it facilitates enhanced security within the AWS network and improves the performance byreducing the latency and bandwidth constraints associated with internet based communication.
AWS VPC Endpoint
Deploying your application in the AWS VPC which doesn’t have an internet connection by default, and the application is required to communicate with S3 service for reading the files and writing the files, in this scenario to make the application communicate with S3, we need a route for public internet using either NAT Gateway, Internet Gateway, or AWS Direct Connect. What if you don’t want to expose any requests being made inside this application to go through the internet?, here comes the concept of VPC Endpoints.
Table of Content
- What are AWS VPC Endpoints?
- AWS VPC Endpoints Architecture
- Types of VPC Endpoints
- What are shared Subnets?
- How to Create AWS VPC Endpoints? A Step-By-Step Guide
- What Are Service Providers?
- What Are Service Consumers?
- What are AWS PrivateLink Connections?
- What are Private Hosted Zones?
- AWS VPC Services List
- AWS VPC Endpoint Pricing
- AWS VPC Endpoint vs Endpoint Service
- Examples of AWS VPC Endpoint
- AWS VPC EndPoint – FAQs