Skip to content
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

Support sts_regional_endpoints configuration #662

Merged
merged 2 commits into from
Sep 19, 2020
Merged

Conversation

mtibben
Copy link
Member

@mtibben mtibben commented Sep 19, 2020

Support the sts_regional_endpoints in the aws config file or via the AWS_STS_REGIONAL_ENDPOINTS env var.

Reference: https://docs.aws.amazon.com/cli/latest/topic/config-vars.html#aws-sts

This may help with #543

@mtibben mtibben merged commit 1afe60d into master Sep 19, 2020
@mtibben mtibben deleted the sts_regional_endpoints branch September 19, 2020 10:36
@mtibben mtibben mentioned this pull request Jan 5, 2021
@ronkorving
Copy link

@mtibben How do I enable this as a user from my config file? This should make AWS Vault run a bit faster for us on the other side of the planet (of us-east-1) I guess. But it's not entirely clear for me from the doc update in this PR on how to do this in my config file.

I've tried

sts_regional_endpoints = regional

But when I execute aws vault exec myprofile -- env |grep AWS I do not see AWS_STS_REGIONAL_ENDPOINTS getting set. Does it only apply to the inner workings of AWS Vault and not set an env var for whatever I end up executing next? If it only applies to internals, is there a way for me to confirm I've configured it right?

@mtibben
Copy link
Member Author

mtibben commented Apr 1, 2021

Yep try with --debug

@ronkorving
Copy link

Works! Awesome! Thank you :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants