AWS DevOps Guru Agent Goes GA and Docker Adds AWS Offload Support
Amazon Web Services announces the general availability of its AI-powered DevOps Guru Agent, while Docker ships native AWS compute offload — letting developers run containers in the cloud directly from Docker Desktop.
Table of Contents
AWS DevOps Guru Agent — Generally Available
Amazon Web Services has announced the general availability of AWS DevOps Guru Agent, an AI-powered service that monitors applications, detects anomalies, and recommends — or autonomously executes — remediation steps.
What DevOps Guru Agent Does
DevOps Guru Agent sits between your application metrics/logs and your on-call engineers. In GA, it can:
- Detect anomalies across CloudWatch metrics, logs, and X-Ray traces
- Correlate root causes across multiple services (e.g., a Lambda timeout caused by an RDS connection pool exhaustion)
- Generate remediation plans in plain English with links to the relevant console pages
- Execute remediations autonomously (in opt-in agentic mode) — scaling groups, restarting tasks, adjusting reserved concurrency
- Notify via PagerDuty, Slack, or OpsGenie with full context
Pricing
DevOps Guru Agent is billed per AWS resource analyzed per hour. The first 100 resource-hours per month are free.
// CloudFormation snippet to enable DevOps Guru Agent
{
"Type": "AWS::DevOpsGuru::ResourceCollection",
"Properties": {
"ResourceCollectionFilter": {
"CloudFormation": {
"StackNames": ["my-production-stack"]
}
}
}
}
Agentic Mode — Autonomous Remediation
The most significant GA addition is agentic mode. When enabled, the agent can take actions within a defined policy boundary:
# Example DevOps Guru Agent policy (IAM-based scope)
allowed_actions:
- ecs:UpdateService
- lambda:PutFunctionConcurrency
- application-autoscaling:RegisterScalableTarget
deny_actions:
- ec2:TerminateInstances
- rds:DeleteDBInstance
The agent logs every autonomous action to CloudTrail and sends a notification before executing.
Docker Desktop 4.40 — AWS Compute Offload
In a separate announcement, Docker shipped Docker Desktop 4.40 with native AWS compute offload. This feature lets developers run containers on AWS infrastructure directly from the docker run command — no ECS or Kubernetes knowledge required.
How It Works
After linking your AWS account in Docker Desktop settings, you can offload any container run to AWS Fargate:
# Run locally (default)
docker run -p 8080:80 nginx
# Offload to AWS Fargate
docker run --cloud aws -p 8080:80 nginx
Docker handles building and pushing the image to ECR, provisioning a Fargate task in your default VPC, forwarding the port to your local machine via a secure tunnel, and tearing down the task when you Ctrl+C.
Use Cases
- Resource-hungry workloads — run an LLM inference server on a
p3.2xlargewithout leaving your terminal - Consistent environments — test against production-like AWS networking without a full staging stack
- Avoid local resource contention — offload build-heavy containers so your laptop stays responsive
Pricing
You pay standard Fargate per-vCPU/per-GB-memory rates. Docker Desktop itself is free for personal use.
Why This Matters Together
These two releases point at the same trend: cloud infrastructure is moving closer to the developer's local workflow. DevOps Guru Agent removes the need to manually triage production incidents, while Docker's AWS offload removes the need to manually set up cloud infrastructure to test at scale. Both reduce the gap between writing code and running it reliably in production.