The AWS Service Quotas That Will Take Down Your Production at 3 Am
The article discusses the challenges faced by AWS users when they encounter service quotas that can disrupt production environments. It highlights the difference between adjustable quotas and hard limits, emphasizing the difficulties in raising limits quickly during critical situations. The author warns that relying on support tickets for quota increases can lead to significant downtime during traffic spikes.
- ▪AWS accounts have two types of limits: adjustable quotas and hard limits.
- ▪Adjustable quotas can take 1–3 business days to increase, which is problematic during urgent situations.
- ▪Hard limits are fixed and cannot be changed, leading to potential service disruptions.
- ▪Users may experience throttling issues, such as Lambda limiting concurrent executions to 1,000 per region.
- ▪The article emphasizes the importance of understanding these limits to avoid production failures.
Opening excerpt (first ~120 words) tap to expand
Member-only storyThe AWS Service Quotas That Will Take Down Your Production at 3 AM (And You Cannot Raise Them Fast Enough)Illya Yalovoy13 min read·Just now--ListenShareHard limits, scaling lags, and the architectural walls that no support ticket can fix.Your pager fires at 3:12 AM. Users are getting 503s. You check the dashboard — Lambda is throttling at 1,000 concurrent executions. You open a quota increase request and see the estimated response time: 1–3 business days. It is Saturday.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Medium.
Discussion
0 commentsMore from Medium
