Skip to content

Add 365-day lifecycle configuration to the CloudTrail log buckets - #223

Open
ale210 wants to merge 1 commit into
mainfrom
203-cloudtrail-bucket-lifecycle
Open

ale210 wants to merge 1 commit into
mainfrom
203-cloudtrail-bucket-lifecycle

Conversation

@ale210

@ale210 ale210 commented Nov 11, 2026

Copy link
Copy Markdown
Member

Closes #203.

Adds an aws_s3_bucket_lifecycle_configuration to each CloudTrail log bucket in terraform/cloudtrail.tf: expire objects after 365 days, abort incomplete multipart uploads after 7. Expiration only — no storage-class transition, since these objects are far below Glacier's 128 KB minimum billable size. Neither bucket has ever had versioning enabled, so no noncurrent-version rule is needed. The file header comment is updated to drop the lifecycle configuration from its list of deliberately omitted items.

Expected plan: 2 to add, 0 to change, 0 to destroy.

Before merging: the first expiration sweep permanently deletes roughly 2022-10 to 2025-11 of management-events history. Confirm nobody relies on it.

terraform/README.md is not regenerated here — it is already behind main and is left for #208.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a lifecycle configuration to the two CloudTrail log buckets

1 participant