-
Notifications
You must be signed in to change notification settings - Fork 910
EC2 Metadata service timeout #980
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
Comments
Are you referring to |
@zoewangg Yeah, that is the class, it does not have adjustable connection timeout settings (like other services do). It might be nice to have adjustable timeouts there as well: Line 35 in 2b8d410
|
At the moment, We have plans to refactor and make them public, tracking in #61. Marking this as a feature request. |
Resolving to track in #61 |
We use a a reverse proxy in front of the ec2 metadata service ( github.com/jtblin/kube2iam ) on our kubernetes cluster to restrict certain namespaces to certain iam roles. It does this by intercepting the call, authenticating the source and making an STS AssumeRole call and passing the credentials back as if the metadata service returned it.
That STS call, of course, takes longer than just a raw call to the metadata service. This often means we get timeouts in our applications that do this.
I've dug through the documentation but haven't found a way to extend the timeout for metadata service calls. Can anyone point me to how I can do this? If it cannot be done consider this a feature request for same.
Expected Behavior
There should be a way for a user of the SDK to adjust the timeout for ec2 metadata service calls.
Current Behavior
We often see timeouts resulting in "Unable to locate credentials"
Possible Solution
Ability to set an env variable or set directly in code the timeout associated with these calls.
Steps to Reproduce (for bugs)
.. it's involved. But if you created a slimmed down similar proxy you could see the problem.
Context
Your Environment
The text was updated successfully, but these errors were encountered: