Thread
#aws
    a

    agreeable-scooter-87411

    4 weeks ago
    Anyone had experience that the EKS init by one person, that passed onto the next person, the second person became unauthorized to do things like create iamserviceaccounts, like because the he is not the cluster creator or some sort?
    q

    quaint-eye-38036

    4 weeks ago
    When you create an Amazon EKS cluster, the AWS Identity and Access Management (IAM) entity user or role, such as a federated user that creates the cluster, is automatically granted system:masters permissions in the cluster's role-based access control (RBAC) configuration in the Amazon EKS control plane. This IAM entity doesn't appear in any visible configuration, so make sure to keep track of which IAM entity originally created the cluster. To grant additional AWS users or roles the ability to interact with your cluster, you must edit the aws-auth ConfigMap within Kubernetes and create a Kubernetes rolebinding or clusterrolebinding with the name of a group that you specify in the aws-auth ConfigMap.
    Ref: https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html