Open
Description
- Do not use the issues tracker for help or support (try Elixir Forum, Slack, IRC, etc.)
- Questions about how to contribute are fine.
Environment
- Elixir & Erlang versions (elixir --version):1.16
- ExAws version
mix deps |grep ex_aws: 2.5.2 (ex_aws_s3: 2.5.2, ex_aws_sts: latest) - HTTP client version. IE for hackney do
mix deps | grep hackney
Current behavior
I have an EKS cluster, when deploying a Deployment using a docker file. The SDK seems to fail to authenticate with the the ServiceAccount that is attached to that deployment.
It seems to default to an instance_role and auth with an IAM role of the nodes in the cluster.
In our example this IAM role does not have permissions to operate with an S3 bucket. Only the IAM role we have configure with the ServiceAccount.
I have checked that the newly create IAM role has succfient permissions and can operate with the relevant S3
Expected behavior
Working within EKS the SDK should work like any other AWS SDK and allow assuming/working with the IAM role that is attached to a Pod/Deployment using a ServiceAccount
Metadata
Metadata
Assignees
Labels
No labels