I got pwned by my cloud costs (troyhunt.com)

Article summary

The author, Troy Hunt, discusses how his cloud costs skyrocketed due to a misconfiguration in his Azure storage account, resulting in an unexpected bill of over $8,000. The issue was caused by a large file exceeding the cacheable size limit set by Cloudflare, leading to excessive bandwidth usage. Hunt explains how he investigated and resolved the issue, and also discusses the importance of monitoring cloud costs and setting up alerts to prevent similar situations. He also shares what he has done to prevent such incidents in the future, including setting up cost alerts and modifying his Cloudflare rules.

Main themes

• cloud costs
• pricing models
• billing alerts
• cache configuration
• cloud providers
• cost management
• transparent pricing
• predatory pricing schemes

What commenters say

• Some commenters argue that cloud providers intentionally make it easy to overspend due to their pricing models.
• Others suggest that setting a hard cap on monthly spend would help prevent unexpected bills.
• A few commenters mention that some cloud providers, such as Hetzner, offer more transparent and limited pricing models.
• There is a disagreement on whether the term 'dark patterns' is an effective way to describe predatory pricing schemes.
• Some argue that cloud providers should be forced by law to offer pay-as-you-go models with hard spending limits.
• Others share their own experiences with unexpected cloud bills and how they were able to resolve the issues.
• A few commenters compare the pricing models of different cloud providers, highlighting the significant differences in costs.
• Some suggest that the lack of instant alerts and the delay in reporting can still lead to significant unexpected expenses.