Getting error while creating config map

[rahulrajm]

terraform version 0.14
Getting Error: Unauthorized while creating config map. Please fix

[im2nguyen]

Hello! Can you check if you have permission to create a config map?

• https://aws.amazon.com/premiumsupport/knowledge-center/eks-api-server-unauthorized-error/
• Local Exec Unauthorized on applying ConfigMap terraform-aws-modules/terraform-aws-eks#612

[rahulrajm]

I have admin privilege to create cluster but I am getting below error while creating the cluster. module.eks.kubernetes_config_map.aws_auth[0]: Creating... Error: Unauthorized

…

On Wed, 3 Feb 2021 at 23:11, Tu Nguyen ***@***.***> wrote: Hello! Can you check if you have permission to create a config map? - https://aws.amazon.com/premiumsupport/knowledge-center/eks-api-server-unauthorized-error/ - terraform-aws-modules/terraform-aws-eks#612 <terraform-aws-modules/terraform-aws-eks#612> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHMJ27CE35HIOIGJC3KIYV3S5GDDLANCNFSM4XBG3WTQ> .

[im2nguyen]

Can you try following the instructions for You're the cluster creator

[rahulrajm]

The instructions are telling about error which we getting after cluster creation. I am hetting below error middle of the cluster creation There is some issue in your code, please correct it or suggest me a stable terraform code

…

On Thu, 4 Feb 2021 at 12:53 AM, Tu Nguyen ***@***.***> wrote: Can you try following the instructions for You're the cluster creator <https://aws.amazon.com/premiumsupport/knowledge-center/eks-api-server-unauthorized-error/> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHMJ27DP2RH35A3BFHAKP4TS5GKPVANCNFSM4XBG3WTQ> .

[im2nguyen]

I haven't been able to replicate it, can you provide more information and the full error message?

[rahulrajm]

I have attached the error log. Please have a look.

…

On Thu, 4 Feb 2021 at 09:09, Tu Nguyen ***@***.***> wrote: I haven't been able to replicate it, can you provide more information and the full error message? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHMJ27GKNWXNXSZLR5ELQ2LS5IJFTANCNFSM4XBG3WTQ> .

[mijhael3000]

terraform version 0.14
Getting Error: Unauthorized while creating config map. Please fix

I solved this changing in my .aws/config file the region from us-west-2 to us-east-2

$ cat ~/.aws/config
[default]
region = us-east-2

[rahulrajm]

@mijhael3000 After making the changes also, getting same error

[im2nguyen]

Can you create an issue in the terraform-aws-eks module repo? They should be able to help you

[siozosdr]

I'm getting the same error as well:

module.eks.kubernetes_config_map.aws_auth[0]: Creating...

Error: Unauthorized

I'm testing with cluster_version="1.19" instead of "1.18" but I don't think that it should matter.
Rest of the resources have been created successfully but not the config_map. If I try to access the EKS cluster from the AWS console I get the message:

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

The AWS documentation only has to do with after creating the cluster which is NOT the case for me as well.
I'm deploying the resources with an iam role that has eks:* permissions on '*'

EDIT: This is happening because I'm deploying the cluster with a specific terraform role. If I deploy the cluster with the Admin user then I can access the cluster from the console as well as get the config_map to be created.

The docs should be more explicit about use cases like this

[alanszlosek]

This should now be fixed by #64 and #65. Please let us know if you are still having issues.