-
Notifications
You must be signed in to change notification settings - Fork 62
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 EC2 metadata service #265
Comments
IMDS uses a hard coded IP/port: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html So under typical configurations, each host has access to a single IMDS and there really is no cross platform way to hand out different credentials to different processes- everything is truly global. |
Hey @synfinatic, thanks a lot for this tool. We have been trying it out in our company to replace Can you estimate how long the implementation of this feature will take? Is there any way we can support the development of this feature, by code contribution or financial sponsoring? |
Hi @marcelmindemann. Code contributions are definitely welcome! That said, I'd love to understand if you just want parity with |
@marcelmindemann I also meant to ask, is the EC2 metadata service the ideal solution or would be the ECS endpoint better? #398 |
The ECS metadata endpoint is required because EC2 requires sudo to run because it is hosted on a protected port 80. So the ECS metadata endpoint is really the better solution. |
Deciding to do ECS (#398) instead of this ticket for now. |
users wishing to vote for this feature should open a new ticket. |
"One of the main uses for us in aws-vault is the metadata service for running lambda's locally and/or vagrant machines"
The text was updated successfully, but these errors were encountered: