AWS Cloud Operations Blog

Telemetry volume and incident counts keep growing while operations headcount stays flat, and coding tools now produce changes faster than most release processes can review them. The AIOps topic on the re:Invent 2026 Cloud Operations (COP) track covers how AI agents handle operational work: investigating incidents, recommending fixes, reviews code changes to catch issues before […]

As organizations continue to scale their cloud presence and bring AI agents into production, effective operations become increasingly critical for success. The AWS re:Invent 2026 Cloud Operations track brings together industry experts, AWS leaders, and customers to share how they modernize monitoring and observability for applications and the AI agents now running alongside them. This […]

1. Introduction A pod on your Amazon Elastic Kubernetes Service (Amazon EKS) cluster is restarting on a memory limit. An automated agent spots it, doubles the memory, and syncs the application. On a quiet afternoon that is a tidy self healing story. During a release window, or on a service that is mid rollout, the […]

Setting meaningful Service Level Objectives (SLOs) is one of the most challenging aspects of running reliable services. Choosing the right reliability targets is where many teams get stuck. Pick a threshold that’s too tight, and you drown in alerts. Pick one that’s too loose, and you won’t catch real problems until customers complain. Many teams […]

When an operations engineer or developer starts an AWS Systems Manager Session Manager session on a managed node, every command they run is captured as a transcript. Any one of those commands is either routine work or the first sign of a security incident. At scale, with hundreds of nodes generating thousands of command entries […]

Introduction Before an AWS DevOps Agent investigation runs its first billable query, you can see what it will cost and decide whether to proceed. The Investigation Cost Guardrail skill brings cost awareness to AWS DevOps Agent, giving your team visibility and control over scope before the investigation begins. This post introduces the Investigation Cost Guardrail, […]

Introduction If you operate AWS Systems Manager (SSM) documents, such as Automation runbooks and Run Command documents, across an AWS Organization, you must decide which accounts can run them. Until now, that meant sharing each document with a list of individual account IDs through the ModifyDocumentPermission API, which accepts up to 1,000 account IDs per […]

When an incident hits at 2 AM, the on-call engineer’s effectiveness depends on what they know about the system, which metrics to check first, what “normal” looks like for this service, and where to find the deployment history. That knowledge often lives in runbooks, internal wikis, and the heads of senior engineers who built the […]

If you manage production incidents, you know the drill. A ServiceNow ticket fires at 2 AM. The on-call engineer wakes up, logs in to Dynatrace, pulls traces and metrics across multiple dashboards, cross-references change records, forms a hypothesis, updates the ticket, and posts findings to Slack. The investigation takes one to three hours, and that’s […]

Security incident triage usually starts cold. An Amazon CloudWatch alarm fires at 2 a.m. because an AWS Identity and Access Management (IAM) access key just created another access key. The responder spends the first 30 minutes assembling evidence from AWS CloudTrail, Amazon CloudWatch Logs, and Amazon Virtual Private Cloud (Amazon VPC) Flow Logs before deciding […]