Access ingest api secret in different aws account#374
Open
Conversation
smohiudd
changed the title
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
1 participant
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.
Description
We have a case where we need to access the MCP keycloak ingest api etl secret from SMCE. This PR implements step 3 from this guide: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_examples_cross.html
The PR also refactors how the custom worker iam policies are recorded. Previously they were listed in variables.tf which made it difficult to handle conditionals. They are now included in
iam.tfas locals.