We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
AWS supports short-term / temporary AWS credentials. The concept is described at https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html, but the basic idea is that in addition to AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY, you provide an AWS_SESSION_TOKEN which is a short-lived token. https://docs.aws.amazon.com/cli/v1/userguide/cli-authentication-short-term.html is an example with the AWS CLI and configuration file.
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_SESSION_TOKEN
I think https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_use-resources.html gives an overview of the flow and links to the spec, but I think the basic idea is to make an initial request to the STS service and include the returned AWS_SESSION_TOKEN where you'd normally use AWS_SECRET_ACCESS_KEY.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
AWS supports short-term / temporary AWS credentials. The concept is described at https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html, but the basic idea is that in addition to
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
, you provide anAWS_SESSION_TOKEN
which is a short-lived token. https://docs.aws.amazon.com/cli/v1/userguide/cli-authentication-short-term.html is an example with the AWS CLI and configuration file.I think https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_use-resources.html gives an overview of the flow and links to the spec, but I think the basic idea is to make an initial request to the STS service and include the returned AWS_SESSION_TOKEN where you'd normally use
AWS_SECRET_ACCESS_KEY
.The text was updated successfully, but these errors were encountered: