Amazon VPC Endpoints Guide

A Virtual Private Cloud (VPC) allows you to have control over your virtual networking environment including the selection of your own IP address range, creation of subnets, and configuration of route tables and network gateways.
VPC Endpoints, a feature of Amazon VPC, enables private connections between your VPC and supported AWS services and VPC Endpoint services powered by PrivateLink.
Why it is important: VPC Endpoints are important as they allow your EC2 instances in your VPC to use private IP addresses to access Amazon S3 and DynamoDB directly, without needing to connect over the Internet or via a VPN or NAT device. This greatly increases the security and privacy of your applications.
How it works: When you create a VPC endpoint, you can specify the VPC in which to create the endpoint, and the service to which to establish the connection.
Exam Tips: Answering Questions on VPC Endpoints: When attending an exam on AWS Solution Architect - Amazon VPC Endpoints, you should remember that VPC Endpoints allow communication to AWS services without crossing the public internet, which enhances privacy and reduces costs. You should be able to differentiate Gateway Endpoint (for services like S3) and Interface Endpoint (for services like EC2). You should know how to write endpoint policies for controlling access. Endpoints do not require an Internet Gateway, a VPN connection, or a separate physical hardware.