AWS Introduces Spend Limits Feature to Control Cloud Costs and Prevent Unexpected Charges Due to Hacking or Forgotten Services

Key summary

A common issue is unexpectedly high cloud service costs due to hacking or forgotten services. Recently, AWS introduced the Spend Limits feature, which previously only provided notifications. Now, users can set a minimum service cost limit of $20. The system will prevent the launch of new services if it is predicted that the limit will be exceeded within 7 days. However, existing services will continue to run. If the limit is exceeded within 5 days, unused services will be stopped. 14 days ago, 4 days before exceeding the limit, services in use will be stopped, starting with the most expensive. If the limit is exceeded, the entire project will be stopped. Data can be recovered within 90 days. This feature is primarily aimed at individual developers and is configured on a per-project basis, not the entire account. The service costs are before tax. Source: AWS Builder.