AWS ECS Mumbai has mood swings - DevOps engineer perspective
Mojahid Ul Haque
DevOps Engineer
As a DevOps engineer, I've basically accepted that AWS ECS Mumbai has mood swings. Once or twice a month, it just… decides it's done with life. Deploy? Maybe. Pull images? If it feels like it. Random crash? Always a crowd pleaser.
And of course, the AWS status page sits there smiling like everything's perfectly normal.
Meanwhile, I'm digging through IAM, logs, task defs, pipelines, wondering if I forgot how computers work… only to realize it's just Mumbai taking a personal day again.
But who gets blamed?
"DevOps can't deploy."
Yes. Clearly, I woke up and told ECS to stop doing its job.
At this point, we just want a little stability and a status page that doesn't gaslight me while the region is on vacation.
Originally posted on LinkedIn
View original postRelated Posts
How I reduced AWS networking costs by 93% while removing public attack surface
I recently tackled a common but expensive challenge in AWS: the hidden cost of public IPv4 addresses. In a setup with dozens of ECS Fargate tasks, my "In-use Public IP" charges...
Scaling Applications on AWS (Real Example)
See how to scale an application on AWS with a real architecture example covering stateless compute, data bottlenecks, caching, queues, and rollout safety.
Stop Leaving AWS Credits Unclaimed - That Outage Might've Owed You Money
Remember the AWS outage on October 20th? Six hours down. Over 100+ services affected. Millions of users impacted. Everyone's talked about the RC multi-region setups, and resilie...