CloudTrail data events
Steps your code never saw, such as Lambda event filters and console actions.
Planned. This isn't built yet. The page is a placeholder for where the docs are headed.
What this page will cover#
- Turning on CloudTrail data events for SQS
- Steps they add to a timeline, such as a Lambda event filter dropping a message, or a send from SNS, S3 or the console
- How these steps are labelled, alongside recorded and inferred ones
Timeline
Everything Trailbeam knows happened to one message ID, built by Trailbeam each time you ask for it. See Reading a timeline.
Message
One item in a queue: a body plus attributes. It stays in the queue until a consumer deletes it or the retention period runs out.
Amazon SQS terms in Vocabulary
Inferred
A step Trailbeam worked out from the steps around it, with no span behind it. It has a window, never a time. In the API,
inferred: true. See Recorded and inferred steps.