<p>Was trying to restrict IAM users with the rbac of AWS EKS cluster. Mistakenly updated the configmap "aws-auth" from kube-system namespace. This removed the complete access to the EKS cluster. </p>

<p>Missed to add the <strong>groups:</strong> in the configmap for the user.</p>

<p>Tried providing full admin access to the user/role that is lastly mentioned in the configmap, But no luck.</p>

<p>Any idea of recovering access to the cluster would be highly appreciable.</p>

<p>The config-map.yaml:</p>

<pre><code>apiVersion: v1
kind: ConfigMap
metadata:
  name: aws-auth
  namespace: kube-system
data:
  mapUsers: |
    - userarn: arn:aws:iam::1234567:user/test-user
      username: test-user
</code></pre>

Sandy
<p>Did a work-around for this issue:</p>

<p>Since the IAM user who created the EKS Cluster by default possess complete access over the cluster, inspite of the aws-auth configmap. Since the IAM user who created, had been deleted, we re-created the IAM user, as it would have the same arn (if IAM user is created with the same name as before).</p>

<p>Once created the user credentials(access &amp; secret keys) for the user, we got back access to the EKS cluster. Following which, we modified the config-map as required.</p>
