4 ms·
This is a terrible idea. S3 charges $0.005 per 1,000 PUT operations. So let's say you want to store 1GB (1e9 bytes) 1,000 bytes at a time, that's 1,000,000 keys
by berkle4455 4y ago
This is a terrible idea. S3 charges $0.005 per 1,000 PUT operations. So let's say you want to store 1GB (1e9 bytes) 1,000 bytes at a time, that's 1,000,000 keys.
$0.005 * (1,000,000 PUT operations / 1,000) = $5.00 to write 1GB. The on-going storage cost I believe would be free since the files themselves are empty.
Meanwhile writing a single 1GB file to S3? Costs you $0.023 per month storage, and the single write cost is $0.000005. It'll take 217 months to cost $5.00
- scarface74 4y agoTrivia: this API is I believe the only documented time that AWS has ever raised prices. It was done just for that reason.
- dexterdog 4y agoIf you track the extortion that AWS charges for egress bandwidth against both inflation and what bandwidth costs on average then they are always raising that rate.
- QuinnyPig 4y agoThey changed the pricing dimension when it was in beta. They've also raised SNS prices in some markets where regulatory fees increased, boosted pricing for domain registration several times, redid the pricing model for IoT Core when it was in beta, and changed the pricing model for AWS Config in ways that are kinda... unfortunate, for a lot of us.
- scarface74 4y agoHow do you know? Who are you suppose to be? I’m kidding, point taken. I listen to your podcast all of the time. You also called a project I was heavily involved in at AWS “This may be the worst AWS naming of 2021.” I took it as a point of nerd pride. Out of all of our bad naming convention, that said a lot.
- hansvm 4y agoIsn't that partially mitigated via S3 Batch?
- berkle4455 4y agoNot to my knowledge? Can you link me to the S3 Batch documentation around PUT'ing multiple files from an external source onto S3?