Audit API Calls with CloudTrail Event History
Query CloudTrail for who created or deleted a resource in a time window so an unauthorized change is attributable.
Task
Configure aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=DeleteBucket --start-time 2026-10-24T00:00:00Z so the cloud resource enforces the control automatically without manual console steps.
When to use this
An audit finds that aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=DeleteBucket --start-time 2026-10-24T00:00:00Z was configured manually and drifted, leaving a resource exposed for two weeks.
Prerequisites
- Terraform or IaC tooling installed
- Cloud provider credentials with target permissions
Steps
1. Configure aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=DeleteBucket --start-time 2026-10-24T00:00:00Z in the project configuration file with the recommended defaults.
aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=DeleteBucket --start-time 2026-10-24T00:00:00Z
Expected output: The configuration is accepted and aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=DeleteBucket --start-time 2026-10-24T00:00:00Z runs without errors on the first invocation.
2. Run the check locally to verify aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=DeleteBucket --start-time 2026-10-24T00:00:00Z produces the expected result before pushing.
pnpm test
Expected output: Local run matches CI behavior; no surprises after push.
3. Add the gate to the CI pipeline so aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=DeleteBucket --start-time 2026-10-24T00:00:00Z blocks merge on failure.
- name: Run add cloudtrail event history
run: pnpm test
Expected output: Pull requests with failing aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=DeleteBucket --start-time 2026-10-24T00:00:00Z are blocked from merging.
Troubleshooting
Problem
The check passes locally but fails in CI
Solution
Pin dependency versions and the runtime to match CI exactly; reproduce with the same Docker image or act.
Problem
Configuration is rejected with a schema error
Solution
Check the tool version matches the config schema; older versions may not support newer fields.
Limitations
- The gate only runs on events that trigger the workflow; locally pushed commits bypass it.
- Configuration drift is possible if someone edits settings outside version control.
Codify the control
Start by measuring the problem. Query CloudTrail for who created or deleted a resource in a time window so an unauthorized change is attributable. The most common mistake is adding the gate without first confirming it catches the issue you care about. Run aws cloudtrail lookup-events –lookup-attributes AttributeKey=EventName,AttributeValue=DeleteBucket –start-time 2026-10-24T00:00:00Z against the current codebase and inspect the output before wiring it into CI.
aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=DeleteBucket --start-time 2026-10-24T00:00:00ZDetect drift
Once the gate is in place, make failures actionable. A failing aws cloudtrail lookup-events –lookup-attributes AttributeKey=EventName,AttributeValue=DeleteBucket –start-time 2026-10-24T00:00:00Z should point to the exact file and line, not a generic error. Pin the tool version in the lockfile so a upstream release does not silently change behavior. Review the gate output in every pull request just like a test result.