Correct one S3 bucket without lifecycle policy


S3 Buckets without a lifecycle policy will not move objects between storage layers or expire objects, causing them to remain in their initial tier perpetually, this is inefficient and can be costly.

This pipeline allows you to specify a single S3 bucket without a lifecycle policy and then either send a notification or attempt to perform a predefined corrective action.

Whilst it is possible to utilise this pipeline standalone (see below), it is usually called from the correct_s3_buckets_without_lifecycle_policy pipeline.


titlestringYesTitle of the resource, to be used as a display name.-
regionstringYesAWS Region of the resource(s).-
notifierstringYesThe name of the notifier to use for sending notification messages.default
notification_levelstringYesThe verbosity level of notification messages to send. Valid options are 'verbose', 'info', 'error'.info
approverslist of stringYesList of notifiers to be used for obtaining action/approval decisions.
default_actionstringYesThe default action to use for the detected item, used if no input is provided.notify
enabled_actionslist of stringYesThe list of enabled actions to provide to approvers for selection.
namestringYesName of the S3 Bucket.-
credstringYesName of the credential to be used for any authenticated actions.-
policystringYesLifecycle policy to apply to the S3 Bucket.{ "Rules": [ { "ID": "Transition to STANDARD_IA after 90 days", "Status": "Enabled", "Filter": {}, "Transitions": [ { "Days": 90, "StorageClass": "STANDARD_IA" } ] }, { "ID": "Transition to GLACIER after 180 days", "Status": "Enabled", "Filter": {}, "Transitions": [ { "Days": 180, "StorageClass": "GLACIER" } ] }, { "ID": "Transition to DEEP_ARCHIVE after 365 days", "Status": "Enabled", "Filter": {}, "Transitions": [ { "Days": 365, "StorageClass": "DEEP_ARCHIVE" } ] } ] }


This pipeline has no outputs.