AWS - VPC Endpoint
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIcz5j4GjYKlcvYoEqmjM-k1w3VbYFcXWb3P8vrJO-2AVbcdoM6G_qLDLbMOwsrHAI7eww82yRlFXf-t7Vu40t57IrcBkfqYKvFSUyW5nZ32hpLYf5GIXrO5UtiAV7MSrTVQVUV4kD1ztVq-rbKvFEeARzQoXLIr9QDv-xdjVDHgMNC2wCMs_uLixU9Yk/s320/63178de0492be32979c9acf7_aws-logo.png)
A VPC endpoint enables customers to privately connect to supported AWS services and VPC endpoint services powered by AWS Private Link. Amazon VPC instances do not require public IP addresses to communicate with the resources of the service. A VPC endpoint enables connections between a virtual private cloud (VPC) and supported services , without requiring that you use an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. We will create two subnets Public and Private. We will test the S3 bucket access from both the subnets. Since the public subnet is connected to the Internet Gateway we should be able to access the S3 buckets from the EC2 instances launched in the Public Subnet. We will try to access the s3 bucket from the Private Subnet. Now, We will create a VPC Endpoint - S3. Next, We need to select the VPC. I created a VPC called "DemoVPC" with Public and Private Subnets. Next is the important...