feat(pipelines): add artifactBucketRemovalPolicy and artifactBucketAutoDeleteObjects props#37516
Open
Zelys-DFKH wants to merge 1 commit intoaws:mainfrom
Open
Conversation
github-actions
bot
added
effort/medium
github-actions
bot
added
the
beginning-contributor
aws-cdk-automation
previously requested changes
Apr 3, 2026
…toDeleteObjects props Adds two optional props to CodePipelineProps that control the lifecycle of the managed artifact bucket created when no explicit artifactBucket is provided: - artifactBucketRemovalPolicy: sets the RemovalPolicy on the managed bucket - artifactBucketAutoDeleteObjects: enables autoDeleteObjects (requires DESTROY policy) Closes aws#36624
Zelys-DFKH
force-pushed
the
fix/pipelines-artifact-bucket-removal-policy
branch
from
0d19c25 to
8ab38a2
Compare
aws-cdk-automation
dismissed
their stale review
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue # (if applicable)
Closes #36624
Reason for this change
When
CodePipelinecreates its own artifact bucket (the default behavior), there is no way to control the bucket's removal policy or enable automatic object deletion. This leaves artifacts behind when a pipeline stack is deleted, requiring manual cleanup or custom workarounds.Description of changes
Added two optional props to
CodePipelineProps:artifactBucketRemovalPolicy: sets theRemovalPolicyon the managed artifact bucketartifactBucketAutoDeleteObjects: enablesautoDeleteObjectson the managed artifact bucket (requiresartifactBucketRemovalPolicy: RemovalPolicy.DESTROY)Both props apply only when no explicit
artifactBucketis provided. Passing them alongside an existingartifactBucketorcodePipelinethrows aValidationError.Describe any new or updated permissions being added
None. The
s3:DeleteObjectand related permissions are handled by the existingautoDeleteObjectscustom resource provider, unchanged.Description of how you validated changes
Added five unit tests to
codepipeline.test.ts:autoDeleteObjectssets up the custom resourceartifactBucketRemovalPolicyis set alongside an existingartifactBucketartifactBucketAutoDeleteObjectsis set alongside an existingartifactBucketartifactBucketAutoDeleteObjectsistruebut removal policy is notDESTROYAll five tests pass.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license