--- title: How Property Finder automated incident management with... description: Property Finder, the MENA property portal, used AWS DevOps Agent to automate incident management end-to-end: an ECS CPU-spike alarm triggers autonomous... canonical: https://daily.dev/posts/how-property-finder-automated-incident-management-with-aws-devops-agent-1xepy01ap twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: How Property Finder automated incident management with AWS DevOps Agent | daily.dev og:description: Property Finder, the MENA property portal, used AWS DevOps Agent to automate incident management end-to-end: an ECS CPU-spike alarm triggers autonomous... og:url: https://daily.dev/posts/how-property-finder-automated-incident-management-with-aws-devops-agent-1xepy01ap og:image: https://api.daily.dev/og/posts/1xepY01aP.png og:image:alt: How Property Finder automated incident management with AWS DevOps Agent og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How Property Finder automated incident management with AWS DevOps Agent **[AWS](https://daily.dev/sources/aws)** · 10 min read · 0 upvotes · 0 comments ## Summary Property Finder, the MENA property portal, used AWS DevOps Agent to automate incident management end-to-end: an ECS CPU-spike alarm triggers autonomous investigation across CloudWatch, CloudTrail, ALB, and Grafana telemetry, posts findings to Slack, creates a Jira ticket, pages the on-call engineer by phone via Grafana IRM, and opens a Draft GitHub PR with an auto-generated fix. A real incident (CPU saturation from conflicting autoscaling policies) was resolved end-to-end in 14 minutes, down from 2-3 days for detection alone. A separate, narrowly-scoped remediation agent with read-only-adjacent guardrails and GitHub MCP access generates Terraform/code fixes as Draft PRs requiring human review; the agent never auto-merges. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How long did it take Property Finder to resolve an ECS CPU saturation incident using AWS DevOps Agent? The full incident lifecycle completed in 14 minutes, from CloudWatch alarm trigger to root cause identification, Slack notification, Jira ticket creation, on-call phone page, and an opened GitHub pull request with the fix. This compares to a prior mean time to resolution of 2 to 3 days for non-critical issues, and 20 to 40 minutes of manual investigation alone before automation. _Teams weighing autonomous incident response can track real production case studies like this one on daily.dev._ ### What caused the ECS service CPU spike to 99% at Property Finder and how was it fixed? The root cause was conflicting CPU and memory target-tracking autoscaling policies: a CPU policy targeting 70% and a memory policy targeting 75%, while actual memory usage sat at only 3-8%, creating 22+ scaling flips and pinning the service at two tasks with no CPU headroom due to a MinCapacity set too low. The fix removed the memory-based policy, raised MinCapacity, and used CPU-only target tracking at 70%. _Engineers debugging conflicting ECS autoscaling policies can find similar real-world fixes surfaced on daily.dev._ ### How does AWS DevOps Agent safely auto-generate remediation code without giving AI agents write access to infrastructure? A separate, narrowly-scoped remediation agent (pr-creation-agent) is invoked only after investigation completes, restricted to a GitHub MCP server as its only external integration, authenticated with a fine-grained, expiring personal access token scoped to specific repositories. Every output is a Draft pull request requiring human review and merge; the agent never auto-merges, and no elevated IAM role is granted. _Developers designing guardrails for AI agents touching infrastructure can follow patterns like this via daily.dev._ ## Similar posts on daily.dev - [AWS Announces General Availability of DevOps Agent for Automated Incident Investigation](https://daily.dev/posts/aws-announces-general-availability-of-devops-agent-for-automated-incident-investigation-o3foudjfb) · InfoQ · 0 upvotes · 0 comments - [Production-Ready Autonomous Incident Resolution with AWS DevOps Agent \(now GA\) and Datadog MCP Server](https://daily.dev/posts/production-ready-autonomous-incident-resolution-with-aws-devops-agent-now-ga-and-datadog-mcp-serve-ndg2ps8n2) · AWS · 0 upvotes · 0 comments - [AWS Debuts “DevOps Agent” to Automate Incident Response and Improve System Reliability](https://daily.dev/posts/aws-debuts-devops-agent-to-automate-incident-response-and-improve-system-reliability-uo2xyxagj) · InfoQ · 1 upvotes · 0 comments - [AWS DevOps Agent — Capabilities, Setup, and What It Actually Does](https://daily.dev/posts/aws-devops-agent-capabilities-setup-and-what-it-actually-does-b16ztfmbs) · AWS Fundamentals · 10 upvotes · 2 comments - [Automate root cause analysis across Datadog and Elasticsearch with AWS DevOps Agent](https://daily.dev/posts/automate-root-cause-analysis-across-datadog-and-elasticsearch-with-aws-devops-agent-pg6b3fzvz) · AWS · 0 upvotes · 0 comments --- Tags: [#aws](https://daily.dev/tags/aws), [#ai-agents](https://daily.dev/tags/ai-agents) [View this post on daily.dev](https://daily.dev/posts/how-property-finder-automated-incident-management-with-aws-devops-agent-1xepy01ap) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"How Property Finder automated incident management with AWS DevOps Agent","url":"https://daily.dev/posts/how-property-finder-automated-incident-management-with-aws-devops-agent-1xepy01ap","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-property-finder-automated-incident-management-with-aws-devops-agent-1xepy01ap"},"datePublished":"2026-09-28T19:09:34.430Z","dateModified":"2026-09-28T19:10:02.346Z","description":"Property Finder, the MENA property portal, used AWS DevOps Agent to automate incident management end-to-end: an ECS CPU-spike alarm triggers autonomous...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e62ee1edf78102587612d42ba8a9b2e3?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e62ee1edf78102587612d42ba8a9b2e3?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"AWS","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"AWS","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/aws","url":"https://daily.dev/sources/aws"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/how-property-finder-automated-incident-management-with-aws-devops-agent-1xepy01ap","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"aws,ai-agents","timeRequired":"PT10M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"AWS","item":"https://daily.dev/sources/aws"},{"@type":"ListItem","position":3,"name":"How Property Finder automated incident management with AWS DevOps Agent"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/how-property-finder-automated-incident-management-with-aws-devops-agent-1xepy01ap#faq","mainEntity":[{"@type":"Question","name":"How long did it take Property Finder to resolve an ECS CPU saturation incident using AWS DevOps Agent?","acceptedAnswer":{"@type":"Answer","text":"The full incident lifecycle completed in 14 minutes, from CloudWatch alarm trigger to root cause identification, Slack notification, Jira ticket creation, on-call phone page, and an opened GitHub pull request with the fix. This compares to a prior mean time to resolution of 2 to 3 days for non-critical issues, and 20 to 40 minutes of manual investigation alone before automation. Teams weighing autonomous incident response can track real production case studies like this one on daily.dev."}},{"@type":"Question","name":"What caused the ECS service CPU spike to 99% at Property Finder and how was it fixed?","acceptedAnswer":{"@type":"Answer","text":"The root cause was conflicting CPU and memory target-tracking autoscaling policies: a CPU policy targeting 70% and a memory policy targeting 75%, while actual memory usage sat at only 3-8%, creating 22+ scaling flips and pinning the service at two tasks with no CPU headroom due to a MinCapacity set too low. The fix removed the memory-based policy, raised MinCapacity, and used CPU-only target tracking at 70%. Engineers debugging conflicting ECS autoscaling policies can find similar real-world fixes surfaced on daily.dev."}},{"@type":"Question","name":"How does AWS DevOps Agent safely auto-generate remediation code without giving AI agents write access to infrastructure?","acceptedAnswer":{"@type":"Answer","text":"A separate, narrowly-scoped remediation agent (pr-creation-agent) is invoked only after investigation completes, restricted to a GitHub MCP server as its only external integration, authenticated with a fine-grained, expiring personal access token scoped to specific repositories. Every output is a Draft pull request requiring human review and merge; the agent never auto-merges, and no elevated IAM role is granted. Developers designing guardrails for AI agents touching infrastructure can follow patterns like this via daily.dev."}}]} ```