| ▲ | maciekkmrk 7 hours ago | |
An entire blog article post to say "read the docs and enable VPC S3 endpoint". It's all in the docs: https://docs.aws.amazon.com/vpc/latest/privatelink/concepts.... >There is another type of VPC endpoint, Gateway, which creates a gateway endpoint to send traffic to Amazon S3 or DynamoDB. Gateway endpoints do not use AWS PrivateLink, unlike the other types of VPC endpoints. For more information, see Gateway endpoints. Even the first page of VPC docs: https://docs.aws.amazon.com/vpc/latest/userguide/what-is-ama... >Use a VPC endpoint to connect to AWS services privately, without the use of an internet gateway or NAT device. The author of the blog writes: > When you're using VPCs with a NAT Gateway (which most production AWS setups do), S3 transfers still go through the NAT Gateway by default. Yes, you are using a virtual private network. Where is it supposed to go? It's like being surprised that data in your home network goes through a router. | ||
| ▲ | jairuhme 5 hours ago | parent [-] | |
> An entire blog article post to say "read the docs and enable VPC S3 endpoint". I think it's okay if someone missed something in the docs and wanted to share from their experience. In fact, if you look at the the s3 pricing page [0], under Data Transfer, VPC endpoints are mentioned at all. It simply says data transfer is free between AWS services in the same region. I think that much detail would be enough to reasonably assume you didn't have to set up additional items to accomplish. | ||