title: Your current user or role does not have access to Kubernetes objects on this EKS cluster
body: <p>Don't know if this is an error from AWS or something. I created an IAM user and gave it full admin policies. I then used this user to create an EKS cluster using the <code>eksctl</code> CLI but when I logging to AWS console with the <strong>root user</strong> I got the below error while trying to access the cluster nodes.</p>
  <p><em><strong>Your current user or role does not have access to Kubernetes objects on this EKS cluster
  This may be due to the current user or role not having Kubernetes RBAC permissions to describe cluster resources or not having an entry in the cluster’s auth config map.</strong></em></p>
  <p>I have these questions</p>
  <ol>
  <li>Does not the root user have full access to view every resource from the console?</li>
  <li>If the above is true, does it mean when I create a resource from the CLI I must login with the same user to view it?</li>
  <li>Or is there way I could attach policies to the root user? Didn't see anything like in the console.</li>
  </ol>
  <p>AWS itself does not recommend creating access keys for root user and using it for programmable access, so I'm so confused right now. Someone help</p>
  <p>All questions I have seen so far and the link to the doc <a href="https://docs.aws.amazon.com/eks/latest/userguide/troubleshooting_iam.html#security-iam-troubleshoot-cannot-view-nodes-or-workloads" rel="noreferrer">here</a> are talking about a user or role created in the AWS IAM and not the root user.</p>