CloudTrail data events
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
AWS CloudTrail records of operations on or inside a resource, such as reading an S3 object or invoking a function, as opposed to management events that record changes to configuration. They are high volume, so trails do not record them unless you ask.
An example, sourced
AWS documents that Amazon Bedrock logs all Agents for Amazon Bedrock Runtime API operations, such as InvokeAgent and InvokeInlineAgent, to CloudTrail as data events. To log InvokeAgent calls, you configure advanced event selectors to record data events for the AWS::Bedrock::AgentAlias resource type. AWS also notes that CloudTrail does not log data events by default because they are often high-volume. The Bedrock page gives the event selector for the agent alias type.
Why it matters here
Data events are where an agent's reads and invocations show up. A trail with only management events cannot answer which objects the agent touched. Cost is the usual reason they are off, which should be an explicit decision in the review.
Related pages
Sources
- https://docs.aws.amazon.com/bedrock/latest/userguide/logging-using-cloudtrail.html, read 10 Nov 2026
Last reviewed 16 Nov 2026.