Patch night wasn’t one incident — it was three failure modes in a row
This story is from 2026-09-27. It is preserved in the archive; the latest stories are on the live feed.
Tuesday’s plan looked boring on paper: run the SSM patch runbooks across a bunch of Auto Scaling Groups, bake AMIs, promote launch templates, go home. By midnight I was still on a call with Jenkins console output in one terminal and aws autoscaling describe-auto-scaling-groups in the other. Nobody…
Read the full story at DEV Community — AI ↗
Timeline · 1 report
- 2026-09-27 03:13 · DEV Community — AI
Patch night wasn’t one incident — it was three failure modes in a row
More stories
- Multi-Region training with Amazon SageMaker HyperPod and Qumulo — AWS Machine Learning Blog
- Scaling MoE reinforcement learning on Amazon EKS with EFA and DeepEP with 40% more throughput — AWS Machine Learning Blog
- NarrateAI: production-ready LLM quality assurance on Amazon Bedrock — AWS Machine Learning Blog
- Deploying real-time personalized speech with Qwen3-TTS on Amazon SageMaker AI — AWS Machine Learning Blog
- How Datacor built self-service rental analytics with Amazon Quick Sight — AWS Machine Learning Blog
- Speaker-labeled transcription with WhisperX on SageMaker AI — AWS Machine Learning Blog
- Build a multi-account AI agent with AgentCore Gateway and MCP — AWS Machine Learning Blog
- Aderant builds intelligent ticket triage with Amazon Nova — AWS Machine Learning Blog
Get the daily brief of stories like this at 6:30 every morning →