36 ms·

That bit on failed multipart uploads invisibly sticking around (and incurring storage cost, unless you explicitly specify some lifecycle magic)... just ugh. An

That bit on failed multipart uploads invisibly sticking around (and incurring storage cost, unless you explicitly specify some lifecycle magic)... just ugh. And I thought one of the S-es was for 'simple'.

teitoklien 2y ago
That S for simple stands for simple ways to skyrocket your expenses
e____g 2y ago
Yes, that sucks. Blame ahenry@, then GM for S3. My proposal was that parts of incomplete uploads would stick around for only 24 hours after the most recent activity on the upload, and you wouldn't be charged for storage during that time. ahenry@ vetoed that.
- vbezhenar 2y ago
  Why would you propose something that makes company earn less money? I'm sure that at Amazon scale, this misfeature earned millions of dollars.
  - spacebanana7 2y ago
    Customer relationships. I recall a Bezos quote along the lines of "It's better to lose a refund than to lose a customer".
Hamuko 2y ago
Yeah, I've definitely treaded on the storage cost landmine. Thankfully it was just some cents in my case, but it's really infuriating how badly the console exposes the information.
scosman 2y ago
“Simple” was coined when the alternative was managing a fleet of servers with disks . Time changes everything.
notatoad 2y ago
this one has cost us many thousands of dollars. we had cron script on a very old server running for almost a decade, starting a multipart upload every night, pushing what was supposed to be backups to a bucket that also stored user-uploaded content so it was normal that the bucket grows in size by a bit every day. the script was 'not working' so we never relied on the backup data it was supposed to be pushing, never saw the files in s3, the bucket grew at a steady and not unreasonable pace. and then this spring i discovered that we were storing almost 3TB of incomplete multipart uploads. and yes, i know that anecdote is just chock full of bad practices.

teitoklien 2y ago

That S for simple stands for simple ways to skyrocket your expenses

e____g 2y ago

Yes, that sucks. Blame ahenry@, then GM for S3. My proposal was that parts of incomplete uploads would stick around for only 24 hours after the most recent activity on the upload, and you wouldn't be charged for storage during that time. ahenry@ vetoed that.

vbezhenar 2y ago
Why would you propose something that makes company earn less money? I'm sure that at Amazon scale, this misfeature earned millions of dollars.
- spacebanana7 2y ago
  Customer relationships. I recall a Bezos quote along the lines of "It's better to lose a refund than to lose a customer".

Hamuko 2y ago

Yeah, I've definitely treaded on the storage cost landmine. Thankfully it was just some cents in my case, but it's really infuriating how badly the console exposes the information.

scosman 2y ago

“Simple” was coined when the alternative was managing a fleet of servers with disks . Time changes everything.

notatoad 2y ago

this one has cost us many thousands of dollars. we had cron script on a very old server running for almost a decade, starting a multipart upload every night, pushing what was supposed to be backups to a bucket that also stored user-uploaded content so it was normal that the bucket grows in size by a bit every day. the script was 'not working' so we never relied on the backup data it was supposed to be pushing, never saw the files in s3, the bucket grew at a steady and not unreasonable pace. and then this spring i discovered that we were storing almost 3TB of incomplete multipart uploads. and yes, i know that anecdote is just chock full of bad practices.