Management and Governance
AWS CloudTrail
On the radar· CloudTrail Lake no longer accepts new customersService that records the actions taken by users, roles, and services in an AWS account as events, whether made from the console, the CLI, the SDKs, or the APIs. It answers who did what, on which resource, and when, for auditing, governance, and compliance.
Exam phrases that point here
«record which user made each API call, when, and from where»
CloudTrail stores an event for every API call, made from the console, the CLI, or the SDKs, with who made it, what action, with what parameters, and what the service responded.
When not: If the question asks how a resource was configured at each point in time or whether it complies with a rule, it is AWS Config. If it asks about CPU usage, latency, or application errors, it is Amazon CloudWatch.
«prove that audit records were not modified or deleted after delivery»
CloudTrail log file integrity validation delivers signed digest files every hour with the hashes of the logs; with them you can check whether a file changed or disappeared.
When not: Validation detects changes, it does not prevent them. If the requirement is to prevent anyone from deleting or overwriting the logs, it is combined with controls on the S3 bucket, such as MFA Delete, bucket policies, or S3 Object Lock.
«record the activity of all accounts in the organization in a single bucket»
An organization trail, created from the management account or a delegated administrator, records the events of all member accounts and delivers them to a single S3 bucket; member accounts cannot modify it.
When not: If what you want to centralize is the compliance status of the configuration, it is an AWS Config aggregator; if it is security findings from multiple services, AWS Security Hub CSPM.
«record who read or wrote objects in an S3 bucket or invoked a Lambda function»
Those operations are CloudTrail data events: high-volume activity on the resources themselves, which you have to enable on the trail for the chosen resources.
When not: Data events are not recorded by default and have a separate cost. A trail with the default configuration records only management events (creating, modifying, or deleting resources).
«detect an unusual volume of API calls»
CloudTrail Insights learns the account's normal volume of calls and generates events when it deviates, for example because of a runaway script.
When not: If the scenario talks about threats, such as compromised credentials or communication with malicious addresses, the clue points to Amazon GuardDuty, which analyzes CloudTrail among other sources.
«react immediately when someone performs a specific action in the account»
With an active trail, API calls arrive as events on the default Amazon EventBridge event bus, where a rule can filter them and send a notification or take corrective action.
When not: Read-only calls (Get, List, Describe) are not received by a normal rule: they require a special rule state. And if the change to watch for is the violation of a configuration rule, AWS Config with remediation is usually a better fit.
Often paired with
- Amazon S3
- Amazon CloudWatch
- Amazon EventBridge