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.

Sign up for GitHub

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

Jump to bottom

More configuration for AssumeRole #63

Closed
riywo opened this issue Apr 1, 2016 · 1 comment
Closed

More configuration for AssumeRole #63

riywo opened this issue Apr 1, 2016 · 1 comment
Labels
feature requests
Projects
2.0.0
Milestone
2.0.0

Comments

@riywo
Copy link
Contributor

riywo commented Apr 1, 2016

Current assume_role_credentials parameter section supports limited configuration for AssumeRole. For example, aws_key_id and aws_sec_key are not passed to STS client, or the duration is fixed.

It is better to have more flexibility for configuration of AssumeRole, but there is no issue reported so far. If there is any request for AssmeRole, please comment here.
@riywo riywo added this to the 2.0.0 milestone Feb 1, 2017
@riywo riywo added this to TODO in 2.0.0 Feb 2, 2017
@riywo riywo moved this from TODO to TODO related to AWS SDK in 2.0.0 Feb 2, 2017
@riywo
Copy link
Contributor Author

riywo commented Mar 13, 2017

#112

@riywo riywo closed this as completed Mar 13, 2017
@riywo riywo moved this from TODO related to AWS SDK to DONE in 2.0.0 Mar 13, 2017
@riywo riywo mentioned this issue Mar 13, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature requests
Projects
No open projects
2.0.0
DONE
Milestone
2.0.0
Development

No branches or pull requests
1 participant
@riywo