From 2 AM alarm to answer: Security Triage with AWS DevOps Agent
AWS Cloud Operations Blog
This article demonstrates how to use AWS DevOps Agent to automate security incident triage by correlating evidence from multiple AWS services when CloudWatch alarms fire.
- Route CloudWatch alarms to AWS DevOps Agent via Lambda forwarder and SNS for automated investigation
- Agent investigates using CloudTrail, VPC Flow Logs, and CloudWatch Logs while remaining read-only through permission guardrails
- Three scenarios map to OWASP Top 10: compromised access keys reading S3 objects, security groups opened to internet, and API abuse attacks
- Agent answers four severity questions: who acted, what changed, what is exposed, and whether anything exploited it
- Responder receives assembled evidence within minutes instead of spending 30 minutes gathering data manually
- Mitigation proposals are drafted for human review; agent cannot execute write actions through role guardrails
AWS DevOps Agent reduces time from alarm to actionable triage by automating evidence correlation while maintaining security boundaries through permission controls.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Aug 19
2026
2026
Use AWS DevOps Agent to triage and route AWS Health event impact
Aug 6
2026
2026
Use CloudWatch syslog and Log Alarms to give AWS DevOps Agent on-premises visibility
Sep 11
2026
2026
AWS DevOps Agent adds bidirectional Slack communication for investigations
Oct 6
2026
2026
Control investigation costs before they start with AWS DevOps Agent
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.