docs: clarification on scoping list secret for secrets #862
Conversation
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
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
markpanganiban
requested review from
gavinelder and
justinegeffen
and removed request for
justinegeffen
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.
Add IAM policy caveat for ListSecrets action
Description
This PR updates the IAM Permissions section in the Seqera documentation to include an important caveat regarding the scope of the ListSecrets action in AWS Secrets Manager.
Specifically, it clarifies that if users choose to restrict the IAM policy scope, the ListSecrets permission must remain set to "Resource": "*". Without this, the Seqera Platform will be unable to delete secrets, potentially causing workflows to become stuck in a running state.
Changes
AWS Secrets Manager actions and permissions reference