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 ?