blog/how-to-assume-an-aws-iam-role-from-a-service-account-in-eks-with-terraform/index #100
Replies: 3 comments
-
|
Great post. Thank you. However, how did you overcome an error stating "Error: error creating IAM policy : MalformedPolicyDocument: Policy document should not specify a principal. |
Beta Was this translation helpful? Give feedback.
-
|
@nataliyalevytska thanks for the kind words! Regarding your error did you get this based on the code in the blog? I had to adjust some of the terraform configurations from our actual production code, and there's a chance it does not work exactly as it should... There is community module for this available that you could use or get some inspiration from: Hopefully this helps and if there's an error with the code in the blog post I would like to get that updated |
Beta Was this translation helpful? Give feedback.
-
|
i get an error with this : FATA[0002] rpc error: code = Unauthenticated desc = error while validating and normalizing app: error validating the repo: error getting k8s server version: the server has asked for the client to provide credentials |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
How to assume an AWS IAM role from a Service Account in EKS with Terraform
In this blog we'll look at how to assume an AWS IAM role from a Service Account that exists within an AWS Elastic Kubernetes Service (EKS) cluster. All provisioned with Terraform.
https://verifa.io/blog/how-to-assume-an-aws-iam-role-from-a-service-account-in-eks-with-terraform/index.html
Beta Was this translation helpful? Give feedback.
All reactions