-
Notifications
You must be signed in to change notification settings - Fork 73
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
Aioboto3 not working on eks. #189
Comments
Ugh this an evil one. It'll need to be fixed in aiobotocore basically by aio-libs/aiobotocore#659 - once I've dealt with some patches here, i'll look into helping the aiobotocore guys out |
Yeah so digging deeper. It gets here - https://github.com/boto/botocore/blob/99a72e5cc689c86419f3cc0d6847da3d8f425148/botocore/credentials.py#L856 and as self._client_creator will return an async version of the botocore client, client.assume_role_with_web_identity would return a coroutine instead of the credentials its expecting hence deepcopy fails. Basically we gotta patch pretty much the entire file... I'll have a think if it can be worked around |
So aio-libs/aiobotocore#659 should be at a point where in theory it'll solve that error you had, do you mind seeing if you can take that pr's code, and see if a simple aiobotocore example works inside eks? |
|
Bear in mind its has 0 testing, so I would not be surprised if you get even more exceptions :D |
Is now tracked here - aio-libs/aiobotocore#779 |
any progress on this? |
This should be solved |
Description
We are using aioboto3==5.0.0 for reading files from s3 bucket inside Kubernetes(EKS) pod. Now we wanted to try out IAM Role for Service Account (IRSA) and as aioboto3==5.0.0 doesn't support IRSA check here. We updated aioboto3==5.0.0 to aioboto3==6.1.0 and then tried all the version above, but it's not working.
What I Did
ERROR:
The text was updated successfully, but these errors were encountered: