No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Hi,
That’s not a pulumi question per se, but we have an aws role issue when creating an EKS cluster. It seems bound to the person creating it (or the aws credentials used by the pulumi aws provider). If someone else tries to interact with it (doing an `aws eks update-kubeconfig` then a `kubectl`) even with aws administrator permissions, we get an Unauthorized error.
How would one properly provision an EKS Cluster with pulumi, with the right role(s)/provider, so that team members can interact afterward on it with `kubectl` without getting an error ?

Ok, found it. If anyone is having the same question:
<https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html>
I’ll update once I have the `pulumi` code corresponding

Ok, there’s a `roleMappings` argument in the `@pulumi/eks` `Cluster` component. That was easier than what I thought :sweat_smile: Hope this will help someone else.