News for hackers. Stuff that matters.
Re:AWS in 2025: The Stuff You Think You Know That's Now Wrong by otterley on Wednesday August 20, 2025 @01:22PM (#44963914)
Gateway endpoints are free. Network endpoints (which are basically AWS-managed ENIs that can tunnel through VPC boundaries) are not free.

S3 can use either, and we recommend establishing VPC Gateway endpoints by default whenever you need S3 access.

(Disclaimer: I work for AWS, opinions are my own.)

Re:AWS in 2025: The Stuff You Think You Know That's Now Wrong by Hikikomori on Wednesday August 20, 2025 @02:00PM (#44964416)
Why don't you have gateway endpoints for all your APIs?
Re:AWS in 2025: The Stuff You Think You Know That's Now Wrong by count on Wednesday August 20, 2025 @09:20PM (#44968153)
The service teams don’t talk to each other…
Re:AWS in 2025: The Stuff You Think You Know That's Now Wrong by mdaniel on Thursday August 21, 2025 @12:36AM (#44969057)
Re:AWS in 2025: The Stuff You Think You Know That's Now Wrong by donavanm on Thursday August 21, 2025 @03:27AM (#44970051)
The original private endpoints implementation required meaningful work from the service teams (ec2 networking, s3, & ddb). It also changed how the "front end" API servers handled requests and how their infrastructure was deployed (at the time?). The newer LB/ENI style privatelink abstracts away _most_ of that "per service" implementation effort at the cost of more per-request/connection work fromthe virtual network. Hence why theres more support from other services, and it includes a cost.