<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/audit-trails-for-autonomous-agents-with-aws-devops-agent-osaf54p2v" -->

---
title: Audit trails for autonomous agents with AWS DevOps Agent
description: AWS DevOps Agent investigates production incidents autonomously and proposes or applies fixes, which creates a need for durable audit trails. The post details...
canonical: https://daily.dev/posts/audit-trails-for-autonomous-agents-with-aws-devops-agent-osaf54p2v
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Audit trails for autonomous agents with AWS DevOps Agent | daily.dev
og:description: AWS DevOps Agent investigates production incidents autonomously and proposes or applies fixes, which creates a need for durable audit trails. The post details...
og:url: https://daily.dev/posts/audit-trails-for-autonomous-agents-with-aws-devops-agent-osaf54p2v
og:image: https://api.daily.dev/og/posts/osAF54P2v.png
og:image:alt: Audit trails for autonomous agents 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.

# Audit trails for autonomous agents with AWS DevOps Agent

**[AWS](https://daily.dev/sources/aws)** · 16 min read · 2 upvotes · 1 comments

## Summary

AWS DevOps Agent investigates production incidents autonomously and proposes or applies fixes, which creates a need for durable audit trails. The post details four data surfaces: an immutable agent journal capturing reasoning, a recommendations API for cross-incident advice, EventBridge lifecycle events, and CloudTrail for API-level accountability. It presents a five-layer reference architecture (lifecycle capture, behavior capture via journal archiving to S3, recommendations snapshotting, control-plane alerting, and Athena/Glue querying) plus correlation scripts (correlate.py and correlate_agent.py) that tie agent findings and recommendations to actual infrastructure changes and approvals. Production guidance covers data volume estimates, pagination, at-least-once delivery handling, S3 Object Lock modes, encryption, common pipeline failures, and their detection/recovery, alongside current limitations like manual correlation and schema evolution risks.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://aws.amazon.com/blogs/devops/audit-trails-for-autonomous-agents-with-aws-devops-agent>

## Questions this post answers

### How do I build an audit trail for AWS DevOps Agent's autonomous investigations and actions?

Combine three surfaces: the agent journal (immutable, ordered records of reasoning and findings, fetched via list-journal-records), EventBridge lifecycle events (Created, In Progress, Completed, carrying the execution_id), and CloudTrail (control-plane API calls). Archive terminal-event journals to S3 keyed on execution_id, poll the recommendations API on a schedule since it has no events, and query everything with Glue and Athena.

_daily.dev surfaces patterns like this for teams designing observability into autonomous AWS agents._

### Why doesn't AWS CloudTrail capture what an autonomous agent actually investigated or concluded?

CloudTrail only records the API calls an agent makes, not its reasoning or conclusions, so it shows that a metric query happened but not that the agent concluded a Lambda was timing out due to a security group blocking egress. AWS DevOps Agent's separate journal captures that reasoning as an immutable, step-by-step record resistant to prompt injection, which CloudTrail cannot provide.

_engineers evaluating agent observability gaps can track this kind of AWS tooling nuance on daily.dev._

### How much storage does the AWS DevOps Agent journal use per investigation?

Journal size scales with investigation complexity: a minimal single-service investigation is about 65 KB (2-3 paginated API calls), a typical multi-signal investigation with 1-2 findings runs 250-340 KB (65-106 calls), and an exhaustive account-wide investigation reaches about 428 KB (150+ calls). At 100 investigations per month averaging 300 KB, storage totals roughly 30 MB monthly.

_teams planning storage and cost budgets for agent-generated audit logs can follow updates like this on daily.dev._

## Community discussion

Top comments from developers on daily.dev.

**@kartiknvj** · 0 upvotes

> The immutable agent journal is the piece most teams skip, and it is exactly what you need when an autonomous fix goes wrong and you have to reconstruct why. The honest note that correlation is still manual matches what I hit: I had an app fully traced and the trace was still useless during the actual incident because nothing tied reasoning to the infra change ([https://dev.to/kartik-nvjk/my-llm-app-was-fully-traced-during-an-incident-the-trace-was-still-useless-3k21](https://dev.to/kartik-nvjk/my-llm-app-was-fully-traced-during-an-incident-the-trace-was-still-useless-3k21)). Are...

## Similar posts on daily.dev

- [Integration with AWS DevOps Agent: Autonomous investigations powered by production context](https://daily.dev/posts/integration-with-aws-devops-agent-autonomous-investigations-powered-by-production-context-bne3y8fst) · Dynatrace · 4 upvotes · 0 comments
- [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
- [As agentic dev tools boom, workflow auditability becomes the constraint](https://daily.dev/posts/as-agentic-dev-tools-boom-workflow-auditability-becomes-the-constraint-vr9ylzsgj) · The New Stack · 0 upvotes · 0 comments
- [Best Practices for Deploying AWS DevOps Agent in Production](https://daily.dev/posts/best-practices-for-deploying-aws-devops-agent-in-production-tjxokmvec) · AWS · 0 upvotes · 0 comments
- [AI-powered incident analysis for Amazon RDS using automated forensic artifacts](https://daily.dev/posts/ai-powered-incident-analysis-for-amazon-rds-using-automated-forensic-artifacts-twjhtywms) · AWS Database Blog · 0 upvotes · 0 comments

---

Tags: [#aws](https://daily.dev/tags/aws), [#ai-agents](https://daily.dev/tags/ai-agents), [#logging](https://daily.dev/tags/logging)

[View this post on daily.dev](https://daily.dev/posts/audit-trails-for-autonomous-agents-with-aws-devops-agent-osaf54p2v)

```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":"Audit trails for autonomous agents with AWS DevOps Agent","url":"https://daily.dev/posts/audit-trails-for-autonomous-agents-with-aws-devops-agent-osaf54p2v","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/audit-trails-for-autonomous-agents-with-aws-devops-agent-osaf54p2v"},"datePublished":"2026-09-28T16:11:19.325Z","dateModified":"2026-09-28T16:11:42.906Z","description":"AWS DevOps Agent investigates production incidents autonomously and proposes or applies fixes, which creates a need for durable audit trails. The post details...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ff831d9ae47ccd815b22b7043590d576?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ff831d9ae47ccd815b22b7043590d576?_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":1,"discussionUrl":"https://daily.dev/posts/audit-trails-for-autonomous-agents-with-aws-devops-agent-osaf54p2v","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"aws,ai-agents,logging","timeRequired":"PT16M"}
{"@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":"Audit trails for autonomous agents with AWS DevOps Agent"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/audit-trails-for-autonomous-agents-with-aws-devops-agent-osaf54p2v","comment":[{"@type":"Comment","text":"The immutable agent journal is the piece most teams skip, and it is exactly what you need when an autonomous fix goes wrong and you have to reconstruct why. The honest note that correlation is still manual matches what I hit: I had an app fully traced and the trace was still useless during the actual incident because nothing tied reasoning to the infra change (https://dev.to/kartik-nvjk/my-llm-app-was-fully-traced-during-an-incident-the-trace-was-still-useless-3k21). Are correlate.py and correlate_agent.py meant to run post-incident, or continuously?","datePublished":"2026-09-28T19:07:44.757Z","url":"https://daily.dev/posts/osAF54P2v#c-TpxGezyl2","author":{"@type":"Person","name":"kartik-nvjk","url":"https://daily.dev/kartiknvj","image":"https://media.daily.dev/image/upload/s--3gGgsVCw--/f_auto/v1781456774/avatars/avatar_TvTVeiMdkRCqWUDullFmy?_a=BAMAMiWQ0"}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/audit-trails-for-autonomous-agents-with-aws-devops-agent-osaf54p2v#faq","mainEntity":[{"@type":"Question","name":"How do I build an audit trail for AWS DevOps Agent's autonomous investigations and actions?","acceptedAnswer":{"@type":"Answer","text":"Combine three surfaces: the agent journal (immutable, ordered records of reasoning and findings, fetched via list-journal-records), EventBridge lifecycle events (Created, In Progress, Completed, carrying the execution_id), and CloudTrail (control-plane API calls). Archive terminal-event journals to S3 keyed on execution_id, poll the recommendations API on a schedule since it has no events, and query everything with Glue and Athena. daily.dev surfaces patterns like this for teams designing observability into autonomous AWS agents."}},{"@type":"Question","name":"Why doesn't AWS CloudTrail capture what an autonomous agent actually investigated or concluded?","acceptedAnswer":{"@type":"Answer","text":"CloudTrail only records the API calls an agent makes, not its reasoning or conclusions, so it shows that a metric query happened but not that the agent concluded a Lambda was timing out due to a security group blocking egress. AWS DevOps Agent's separate journal captures that reasoning as an immutable, step-by-step record resistant to prompt injection, which CloudTrail cannot provide. engineers evaluating agent observability gaps can track this kind of AWS tooling nuance on daily.dev."}},{"@type":"Question","name":"How much storage does the AWS DevOps Agent journal use per investigation?","acceptedAnswer":{"@type":"Answer","text":"Journal size scales with investigation complexity: a minimal single-service investigation is about 65 KB (2-3 paginated API calls), a typical multi-signal investigation with 1-2 findings runs 250-340 KB (65-106 calls), and an exhaustive account-wide investigation reaches about 428 KB (150+ calls). At 100 investigations per month averaging 300 KB, storage totals roughly 30 MB monthly. teams planning storage and cost budgets for agent-generated audit logs can follow updates like this on daily.dev."}}]}
```

