# How to see recent CloudTrail events for a user

How-to guides · Updated 17 November 2026

**Short answer:** In the CloudTrail console open Event history, set the filter to User name and enter the user, role session or SSO user name. From the CLI, run aws cloudtrail lookup-events with the Username lookup attribute. Event history covers the last 90 days of management events in one Region, so repeat for each Region (and us-east-1 for IAM and other global services).

## Console steps

1. Open **CloudTrail > Event history** in the Region you care about.
2. Change the lookup attribute to **User name** and enter the name.
3. Set a time range, then open an event to see the full JSON: source IP, user agent, request parameters and errors.

What to enter as the user name depends on how they signed in:

| Identity | User name in CloudTrail |
|---|---|
| IAM user | The IAM user name, for example `ci-bot` |
| Assumed role | The role *session* name, for example `alice@example.com` for many SSO setups, or whatever the caller passed as `--role-session-name` |
| IAM Identity Center user | Usually their Identity Center user name as the session name of the `AWSReservedSSO_...` role |
| Root | `root` |

## CLI steps

```
aws cloudtrail lookup-events --region eu-west-2 \
  --lookup-attributes AttributeKey=Username,AttributeValue=alice@example.com \
  --start-time 2026-11-16T00:00:00Z --max-results 50 \
  --query 'Events[].[EventTime,EventSource,EventName,Resources[0].ResourceName]' --output table

# Only changes (exclude read-only calls)
aws cloudtrail lookup-events --region eu-west-2 \
  --lookup-attributes AttributeKey=Username,AttributeValue=alice@example.com \
  --query 'Events[].CloudTrailEvent' --output text \
| jq -r 'select(.readOnly == false) | [.eventTime, .eventName, .sourceIPAddress] | @tsv'
```

`lookup-events` takes one lookup attribute per call and is rate-limited (a couple of requests per second per account per Region), so page slowly in scripts. Other useful keys are `AccessKeyId`, `EventName` and `ResourceName`.

## Beyond 90 days or across Regions

- **A trail to S3 and CloudWatch Logs** keeps events as long as you retain them. With the trail sent to a log group, a Logs Insights query searches all Regions at once:

  ```
  fields eventTime, eventSource, eventName, awsRegion, sourceIPAddress
  | filter userIdentity.arn like /alice@example.com/
  | filter eventName not like /^(Get|List|Describe|Lookup)/
  | sort eventTime desc
  | limit 100
  ```

  See [CloudTrail who-did-what queries](https://cloudconsole.dev/logs-insights/cloudtrail-who-did-what).

- **CloudTrail Lake** supports SQL across accounts and Regions if your organisation uses it.

- **Data events** (S3 object reads and writes, Lambda invokes) are never in event history; they only appear if a trail or event data store records them.

## Common mistakes

- **Searching the wrong Region.** Event history is per Region; console sign-ins and IAM changes are recorded in us-east-1 for most accounts.
- **Searching by role name.** For assumed roles, the user name is the session name; search by `ResourceName` or use Logs Insights on `userIdentity.arn` to match the role.
- **Expecting events instantly.** Events typically appear within about five minutes of the call.

## Questions

### How do I see what a user did in AWS?

In CloudTrail Event history, filter by User name, or run aws cloudtrail lookup-events with AttributeKey=Username. Check each Region you use.

### How far back does CloudTrail event history go?

90 days of management events per Region. For longer, use a trail delivering to S3 or CloudWatch Logs, or CloudTrail Lake.

### Is CloudTrail enabled by default?

Event history is available by default for the last 90 days of management events. A trail or event data store is needed to keep events longer or record data events.

## When this happens away from your desk

Checking who changed something is a common first step in an incident. CloudConsole, a phone app for AWS, is being built to show alarms, logs and resources on your phone, which helps you follow up on a suspicious change quickly.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [Working with CloudTrail event history](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/view-cloudtrail-events.html)
- [LookupEvents (CloudTrail API Reference)](https://docs.aws.amazon.com/awscloudtrail/latest/APIReference/API_LookupEvents.html)

## Related

- [How to find who deleted a resource in AWS](https://cloudconsole.dev/how-to/find-who-deleted-aws-resource)
- [How to check who stopped an EC2 instance in CloudTrail](https://cloudconsole.dev/how-to/find-who-stopped-ec2-instance)
- [CloudTrail in CloudWatch Logs Insights: who did what](https://cloudconsole.dev/logs-insights/cloudtrail-who-did-what)
- [How to check which AWS account the CLI is using](https://cloudconsole.dev/how-to/check-who-is-logged-in-aws-cli)
- [AWS incident response checklist](https://cloudconsole.dev/how-to/aws-incident-response-checklist)
- [How to add my IP to an AWS security group](https://cloudconsole.dev/how-to/add-my-ip-to-security-group)

---

Source: https://cloudconsole.dev/how-to/see-cloudtrail-events-for-user

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
