• 👍Maximum Derek👍@discuss.tchncs.de
    ·
    edit-2
    1 year ago

    I once set an S3 lifecycle setting that accidentally affected 3 years worth of logs to Glacier. The next morning I woke up to a billing alert and an AWS bill with an extra $250k in charges (our normal run rate was $30k/month at the time). Basically I spent my entire add annual cloud budget for the year overnight.

    Thankfully after an email to our account rep and a bunch of back and forth I was able to get the charges reduced to $4,300.

      • 👍Maximum Derek👍@discuss.tchncs.de
        ·
        1 year ago

        If I never have to buzz into another colo and stand in the exhaust of hundreds of servers again, it's worth every single penny. If I never have to plan for capacity weeks to years in advance again, its worth every penny.

    • railsdev@programming.dev
      ·
      1 year ago

      I made this mistake but honestly? AWS is the most confusing clusterfuck of all time. I can’t stand it and refuse to use it for personal projects.

      For me the problem came down to four conflicting sources on AWS regarding tiers and then another problem with the SDK. The SDK didn’t match the tiers at all so “archive” meant Glacier for some reason. 👎