Add example policy to AWS secrets engine for AssumeRole that will still be able to rotate itself #30747
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
…ne_sts_assume_role_policy_example
…ne_sts_assume_role_policy_example
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.
Description
Adds documentation and an example policy for STS credential types to be able to rotate themselves.
Note I have tested this exact policy in my lab and also in this example repo for dynamic auth 8000 hashicorp/terraform-dynamic-credentials-setup-examples#31
Preview: https://vault-i4qzmdcu7-hashicorp.vercel.app/vault/docs/secrets/aws#policies-for-sts-credentials