News for hackers. Stuff that matters.
Re:S3 Files and the changing face of S3 by deepsun on Wednesday April 08, 2026 @12:31AM (#47685275)
> directly streamed from the underlying S3 bucket, which is free.

No reads from S3 are free. All outgoing traffic from AWS is charged no matter what.

Re:S3 Files and the changing face of S3 by simtel20 on Wednesday April 08, 2026 @02:07AM (#47685991)
Reads from s3 via an s3 endpoint inside a vpc to an interface inside of that vpc is not billed.
Re:S3 Files and the changing face of S3 by deepsun on Wednesday April 08, 2026 @04:45PM (#47696031)
S3 GET operations are billed anyway.

Traffic may be free, but not the operations.

Re:S3 Files and the changing face of S3 by MontyCarloHall on Thursday April 09, 2026 @10:09AM (#47704000)
S3 GET requests have negligible cost, at $0.0004/1000 requests. Upload requests are $0.005/1000, which is also negligible.
Re:S3 Files and the changing face of S3 by deepsun on Thursday April 09, 2026 @06:54PM (#47711346)
I object, we once paid $40k for that "negligible cost".
Re:S3 Files and the changing face of S3 by simtel20 on Thursday April 09, 2026 @12:59PM (#47706158)
Ok, but to be clear you said all outgoing traffic is charged. The API call price is something else, it's not part of the outgoing traffic.
Re:S3 Files and the changing face of S3 by deepsun on Thursday April 09, 2026 @06:53PM (#47711339)
Yes, and stand by it: > All outgoing traffic from AWS is charged no matter what.

Your example with VPC endpoints does not leave AWS.

Sorry for the confusion you probably thought about outgoing from S3, but I mean outgoing from AWS.