← Back to context

Comment by dirkk0

7 days ago

same here, I am still in shock. took me 10 minutes to find the 'operational issue' message in the dashboard. longest 10 minutes of my life.

24 comments

dirkk0

Reply
charles_f  6 days ago

Can you not set spending limits in AWS?

  • inigyou  6 days ago

    No you can't. Spending limits imply realtime billing backend flows and they also imply deleting all your data so that you don't pay for storage.

    • benterix  6 days ago

      I heard this false justification already in 2007, in spite of many customers asking for it.

      Incidentaly, smaller competitors solved this issue decades ago, while the big cloud decided it is more convenient never to implement it.

      4 replies →

    • handoflixue  6 days ago

      Realtime billing seems entirely within the abilities of AWS.

      "Limits except for Storage" seems even easier - I don't think I've ever heard of a storage-based billing story, although I'm sure one or two exist

      7 replies →

    • SAI_Peregrinus  6 days ago

      > and they also imply deleting all your data so that you don't pay for storage.

      Not necessarily. They could imply that your storage becomes inaccessible immediately, but only gets deleted after some time period (say, 1 month). What spending limits do depends on the implementation.

      3 replies →

    • prmoustache  6 days ago

      Storage could switch to read only.

      That would mean an outage but that is still better than going bankrupt and teach you a thing or two about monitoring.

  • perching_aix  6 days ago

    Not only can you not set limits, even the alarms are not real time. So it is entirely possible to get on the hook for terrifying amounts of money and not know until it's all too late.