feat: support external IDs when assuming a role with a custom resource #33964
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.
Reason for this change
We want to use the
AwsCustomConstruct
for making calls in another account while assuming a role. As a security mitigation, our cross account role requires an external ID. This change allows theAwsCustomConstruct
to optionally use external IDs.Description of changes
Add
assumedRoleExternalId
as an optionalAwsCustomConstruct
parameter and use it when making cross-account calls.Describe any new or updated permissions being added
None
Description of how you validated changes
Unit and integ tests.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license