fix(codepipeline): replace account root principal with pipeline role in trust policy for cross-account actions (under feature flag) #34074
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)
GHSA-5pq3-h73f-66hr
Reason for this change
See GHSA for details.
Description of changes
Added new feature flag
@aws-cdk/pipelines:reduceCrossAccountActionRoleTrustScope
When the feature flag
@aws-cdk/pipelines:reduceCrossAccountActionRoleTrustScope
is set to true:roleName
toPhysicalName.GENERATE_IF_NEEDED
Describe any new or updated permissions being added
Cross-account action role trust policy is scoped with condition key
ArnEquals
when feature flag is enabled:Description of how you validated changes
Added integration tests for S3, StepFunction, and Cloudformation codepipeline actions and manually verified that the cross-account action was successfully completed (reading S3 bucket, invoking state machine, and deploying a cloudformation stack in the cross-account).
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license