I had this problem and, eventually, I figured out it had to do with the CLI.  I thought it was a bug but it seems that it's expected behavior.  (I built the EKS cluster using Terraform.)

Some text on this page helped me figure it out:[ https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html]()

> You can specify an IAM role ARN with the --role-arn option to use for authentication when you issue kubectl commands. Otherwise, the IAM principal in your default AWS CLI or SDK credential chain is used. You can view your default AWS CLI or SDK identity by running the aws sts get-caller-identity command.

Specifically, it's this sentence: *Otherwise, the IAM principal in your default AWS CLI or SDK credential chain is used.*

I have several profiles configured for the AWS CLI.  The only profile used is the **default** one.  The others are ignored.

My fix was to create and export two environmental variables with the corresponding information:
```
aws_access_key_id
```
 and 

```
aws_secret_access_key
```

After I did this, things worked as expected.

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

I had this issue and created a working example of how to update the automatically created aws-auth config map for an existing EKS cluster using terraform: 
https://github.com/jamiemo/k8s-eks-aws-auth-configmap

If you created a cluster, and you are using the same IAM user, and  you still get errors like "error: You must be logged in to the server (the server has asked for the client to provide credentials)", "Identity is not mapped", "Your current IAM principal doesn't have access to Kubernetes objects on this cluster. This might be due to the current principal not having an IAM access entry with permissions to access the cluster." from CLI (kubectl), CloudWatch, and Console respectively, then you have to go to the cluster from the AWS console, access tab, create access entry, select the ARN of your principal (you can see it from CLI with command aws sts get-caller-identity), add access policy, select AmazonEKSAdminPolicy, create and go back to the access tab, click on the access entry you added for your user ARN, add access policy, select AmazonEKSClusterAdminPolicy and try running the kubectl commands again.

is the identity mapping configuration supporting wildcards on ***aws-auth***? like:
```
mapRoles: |
  - rolearn: arn:aws:iam::XXXXXXXXXXXX:role/testrole-*
    username: testrole
    groups:
      - system:masters
```

When running this command: 
```
kubectl edit configmap aws-auth --namespace kube-system
```
You receive this error now:
Error from server (NotFound): configmaps "aws-auth" not found

A quick search brings up [this AWS documentation link](https://docs.aws.amazon.com/eks/latest/userguide/auth-configmap.html) stating that "The aws-auth ConfigMap is deprecated. The reccomended method to manage access to Kubernetes APIs is Access Entries."

So unfortunately, it seems like most of this article is now out-of-date.

I have created eks and continuously trying to connect from windows cli, but always throwing error. I am able to check aws resources from cli also able to see cluster and nodegroup with command like
eksctl get iamidentitymapping --cluster myeks_cluster1

but getting issue with kubectl
E0928 20:24:40.071813    7228 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"

C:\Windows\System32>eksctl get iamidentitymapping --cluster myeks_cluster1
Error: getting auth ConfigMap: Unauthorized


C:\Windows\System32>kubectl version
Client Version: v1.31.0-eks-a737599
Kustomize Version: v5.4.2
error: You must be logged in to the server (the server has asked for the client to provide credentials)




C:\Windows\System32>kubectl get pods -v=10

  "metadata": {},
  "status": "Failure",
  "message": "the server has asked for the client to provide credentials",
  "reason": "Unauthorized",
  "details": {
    "causes": [
      {
        "reason": "UnexpectedServerResponse",
        "message": "unknown"
      }
    ]
  },
  "code": 401
}]
error: You must be logged in to the server (the server has asked for the client to provide credentials)



pls help!

I use kubectl commands to connect to the Amazon Elastic Kubernetes Service (Amazon EKS) API server. I received the message "error: You must be logged in to the server (Unauthorized)".

Resolve the unauthorized server error for the Amazon EKS API server

How do I resolve the error "You must be logged in to the server (Unauthorized)" when I connect to the Amazon EKS API server?

Containers

Migrating Microsoft SQL Server workloads to the AWS Cloud

How do I resolve "error: You must be logged in to the server (Unauthorized)" errors when connecting to an Amazon EKS cluster from CodeBuild?

How do I resolve the error "Unauthorized to perform action due to private marketplace eligibility"?

How do I connect to a private Amazon EKS cluster endpoint from outside the Amazon VPC?

How do I troubleshoot connectivity issues with the API server endpoint of my Amazon EKS cluster?

kubectl error You must be logged in to the server (Unauthorized) when accessing EKS cluster

Unable to access EKS cluster from EC2 instance, despite being able to access other clusters. "couldn't get current server API group list: the server has asked for the client to provide credentials"