-
Notifications
You must be signed in to change notification settings - Fork 4.4k
VAULT-32804: Add STS Fallback parameters to secrets-aws engine #29051
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…cascading fallbacks
This reverts commit 6124b6c.
CI Results: |
Build Results: |
Co-authored-by: Robert <17119716+robmonte@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, LGTM! I added a few suggestions but they should not hold this up.
builtin/logical/aws/client.go
Outdated
return nil, fmt.Errorf("error reading root configuration: %w", err) | ||
var configs []*aws.Config | ||
|
||
// I'm not sure this is a valid scenario, but the previous code had it as a case. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this is possible since none of the aws/config/root
fields are required by the API as they can be either set to defaults or the environment. i.e., I don't believe it is required to explicitly call aws/config/root
and in that case entry will be nil.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated the comment to reflect this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please apply the formatting fix before merging. Otherwise lgtm
Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --------- Co-authored-by: Robert <17119716+robmonte@users.noreply.github.com> Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
Description
Adds two fields,
sts_fallback_endpoints
andsts_fallback_regions
to allow credential requests to try other sts regions if the first one fails.To test this one, set up a
secrets/aws
mount in the usual way:Now, 'break' us-west-1 somehow, (I suggest messing with
/etc/hosts
), and you should get a failure:Experiment with breaking and unbreaking the route to AWS servers - the credential should succeed as long as one sts domain works.
TODO only if you're a HashiCorp employee
in the PR description, commit message, or branch name.