Add missing permission to assume Cross-Account-Org R/O role #509
Conversation
This file contains 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
**Why?** The Generate Pipeline Input lambda function tried to assume into the cross-account access role, to read the organization API. This was not allowed, as it was not permitted by the cross-account access role as a trusted role that can assume into the read-only role in the management account. **What?** Addressed by adding a specific role name for the role that is used by the Generate Input lambda function. Plus putting that role on the allowed list of roles that are allowed to assume the cross-account access role for read-only access to the organization API.
StewartW
approved these changes
Aug 31, 2022
javydekoning
approved these changes
Aug 31, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why?
The Generate Pipeline Input lambda function tried to assume into the cross-account access role, to read the organization API.
This was not allowed, as it was not permitted by the cross-account access role as a trusted role that can assume into the read-only role in the management account.
What?
Addressed by adding a specific role name for the role that is used by the Generate Input lambda function. Plus putting that role on the allowed list of roles that are allowed to assume the cross-account access role for read-only access to the organization API.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.