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

Multiple simultaneous credentials #51

Open
copumpkin opened this issue May 1, 2015 · 3 comments
Open

Multiple simultaneous credentials #51

copumpkin opened this issue May 1, 2015 · 3 comments

Comments

@copumpkin
Copy link
Contributor

If I visit http://169.254.169.254/latest/meta-data/iam/security-credentials/, I see hologram-access in there with the usual credentials in it.

Note that although Amazon does not currently support multiple simultaneous roles, the URL scheme was clearly set up to allow for it.

I'm wondering (assuming that it doesn't break aws-cli, boto, and other major tools) if we could possibly allow a particular hologram agent to serve up multiple credential sets simultaneously, for APIs that are aware of it. In practice, this would just lead to there being multiple entries under security-credentials. If it does end up breaking existing APIs, we could also add a custom "revision" to the top level.

My use case is writing handy developer tools that know about Hologram and wants simultaneous access to multiple AWS accounts/roles. For example, I would like a simple cost-monitoring widget in my menubar that can talk to a particular Amazon account/role regardless of my current Hologram role.

@gaylatea
Copy link
Contributor

gaylatea commented May 1, 2015

https://github.com/boto/boto/blob/bbbf9d248856db997080f51805575f0634da4090/boto/provider.py#L379 details how at least that works, and most things are based off of how boto does it. Looks like your idea should be fine, although I'll be interested in how the CLI and other tools interact with having multiple Hologram roles active. 👍

@copumpkin
Copy link
Contributor Author

Yeah. It might still be good hygiene to use a new top-level revision for other implementations that aren't so graceful when they find unexpected information.

@copumpkin
Copy link
Contributor Author

#61 could also allow for this on linux

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

No branches or pull requests

2 participants