-
Notifications
You must be signed in to change notification settings - Fork 0
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
Access from within EKS from another account still results in Access Denied #1
Comments
EKS is different. You need different trust - https://docs.aws.amazon.com/eks/latest/userguide/associate-service-account-role.html |
Hi, @jangaraj @jeffbeagley
|
I annotated my service account with a remote role:
And in account A configured IAM role and OIDC provider for my EKS cluster:
|
I have the following resources in Account A:
Account B has the following:
I provided the External ID and new IAM Role's ARN from Account B into Grafana that is running within Account A and I still receive the following
User: arn:aws:sts::<accountA>:assumed-role/monitoring-role/<session> is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::<AccountB>:role/monitoring-role-dev
Have you gotten this to work from EKS?
The text was updated successfully, but these errors were encountered: