-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
web credentials not supported #779
Comments
It turns out the primary culprit is in I worked around the problem by using a non-aio botocore session to refresh credentials with the following subclass:
This is a kludge, since it involves making a synchronous botocore api call in the middle of async code, but it seemed to get the job done in my case. |
we're working on this, see #619 + #659 with https://gist.github.com/thehesiod/05298c1c89c7b5a38da0abc4ccbed7b7 workaround until we get this done |
@snstanton you mind testing the changes in #659, in theory the web identity assume role auth should work with those changes |
I have applied the patch and can confirm that the test case above does appear to work now. Thanks for the update! |
Nice! We'll merge the changes soon as I think we're pretty much there |
Describe the bug
I am attempting to connect in a context with web credentials by setting
AWS_WEB_IDENTITY_TOKEN_FILE
. This works with botocore. When I try the same code in aiobotocore, it fails.Here is a sample script that demonstrates the failure:
This results in the following stack trace:
pip freeze results
aiobotocore==0.12.0
aiohttp==3.6.2
aioitertools==0.5.1
async-timeout==3.0.1
attrs==19.3.0
botocore==1.15.15
chardet==3.0.4
docutils==0.15.2
idna==2.9
jmespath==0.9.5
multidict==4.7.5
python-dateutil==2.8.1
six==1.14.0
urllib3==1.25.8
wrapt==1.12.1
yarl==1.4.2
Environment:
The text was updated successfully, but these errors were encountered: