S3 endpoints
Prior to the creation of S3 endpoints, all data being accessed from S3 traversed the public internet. If you had private information that you were passing from a private S3 bucket to a resource in a private subnet in your Virtual Private Cloud (VPC), then not only did this pose some security risks, but it also required some extra networking to allow the resources in the private subnet to talk to the internet so that the S3 buckets that you wanted to access could be uploaded to and downloaded from.
If we have resources in a private subnet of a VPC that do not have a public route to the internet via a NAT instance or a NAT gateway, then we would not be able to access items in our S3 buckets without setting up that NAT instance, or we can make a more secure connection by using an S3 endpoint.
An S3 endpoint, which is a gateway endpoint, allows us to add an entry to the route table of our VPC. By adding this endpoint, we can now bypass the public internet with both our...
