News for hackers. Stuff that matters.
Re:We Saved $500k per Year by Rolling Our Own S3 by sema4hacker on Saturday October 25, 2025 @04:30PM (#45706734)
I'm always amazed by how firms let their AWS expenses get so huge before doing cheaper homegrown solutions.
Re:We Saved $500k per Year by Rolling Our Own S3 by RandomException on Saturday October 25, 2025 @06:51PM (#45707601)
They usually don't make sense optimizing before achieving these levels of expenses. I mean, for a really long time the expenses are so low that it would cost more to engineer these solutions in the first place, and then they suddenly run through the roof exponentially.

But mainly, priorities and "it's not that much in comparison to all else". And perhaps not even tracking the costs properly :)

Re:We Saved $500k per Year by Rolling Our Own S3 by BobbyTables2 on Saturday October 25, 2025 @09:21PM (#45708316)
I see the practical angle but I still don’t get why companies are so happy to park their private internal data in S3.

They have that much faith that the world’s biggest target will never be hacked nor hire a dishonest admin?

Re:We Saved $500k per Year by Rolling Our Own S3 by beached_whale on Saturday October 25, 2025 @11:29PM (#45708923)
It doesn't feel unlikely they would be ordered by a government to share data too.
Re:We Saved $500k per Year by Rolling Our Own S3 by ronbenton on Saturday October 25, 2025 @11:37PM (#45708952)
$500K is like 1 or 2 fully loaded engineer salaries in the US. It’s not all that expensive.
Re:We Saved $500k per Year by Rolling Our Own S3 by gigatree on Saturday October 25, 2025 @11:44PM (#45708977)
I wonder if there’s a point at which AWS decides it would be more financially responsible to make lower margins in order to keep more customers.
Re:We Saved $500k per Year by Rolling Our Own S3 by LeFantome on Sunday October 26, 2025 @12:53AM (#45709244)
Sure. But that point is probably not when they have 40% of the public cloud market.
Re:We Saved $500k per Year by Rolling Our Own S3 by mannyv on Sunday October 26, 2025 @12:28AM (#45709138)
It's strange that they didn't try to negotiate lower pricing or just use another storage service.

Or, just have the lambda delete the file or change its storage tier once processing is done.

Or, just use a lambda instead of a proxy.

Or, just use cloudflare.

Many times "why not" is more interesting than "why."

Re:We Saved $500k per Year by Rolling Our Own S3 by merb on Sunday October 26, 2025 @02:44AM (#45709647)
Just reading the blog post makes me wonder if they really saved 500k. How long did it take them to build the solution, how many people built it, how much does the new service cost while it’s running? How many ops ours does the new service need? The blog goes into many details that I doubt that they built it in less than a month. So maybe they will save money over years but they probably lost money while building the new solution
Re:We Saved $500k per Year by Rolling Our Own S3 by 3abiton on Sunday October 26, 2025 @09:14PM (#45716425)
That was a fun read, great planning, and testing strategy!