Error running command to update_config_map_aws_auth

[terraform-aws-modules]

Error running command to update_config_map_aws_auth

[brandonjbjelland]

Hey @dperic123 -

I tried to fix this before releasing the latest version and that latest tag should be working. Can you try using the latest version of the module (1.3.0) and see if this still happens? Also, just to be sure, make sure you've glanced at the readme and installed the necessary authenticator binary.

@ozbillwang - this is the exact problem I saw and solved that we discussed elsewhere. Im unsure when it was introduced as a problem but likely between 1.1.0 and 1.2.x

[ozbillwang]

@brandoconnor

That's not the problem. The error is about the naming of aws-iam-authenticator, it used to be called heptio-authenticator-aws.

kubernetes-sigs/aws-iam-authenticator@678cdff

So just copy it, rename to aws-iam-authenticator and put it in /usr/bin or /usr/local/bin, this problem should be fixed.

[dperic123]

Let me test. I'm using a windows jump box and set it in the environment variables.

[dperic123]

Looks like the error I get now is:

• null_resource.update_config_map_aws_auth: Error running command 'kubectl apply -f .//config-map-aws-auth_EKSClusterTes
  t.yaml --kubeconfig .//kubeconfig_EKSClusterTest': exit status 1. Output: error: You must be logged in to the server (th
  e server has asked for the client to provide credentials)

[brandonjbjelland]

Sorry, @ozbillwang I misread the error but it presents a similar error to the path issue I saw.

@dperic123 - I can't say I've tried this on Windows yet aside from Linux within Windows (WSL). Your AWS credentials should be assumed from your shell that ran terraform and any other authentication bits should be contained in the config files terraform created.

[dperic123]

Hey so I got it working! Now how do I connect to the actual EKS cluster to set up the dashboard?
The connection to the server localhost:8080 was refused - did you specify the right host or port?

So I was able to set up the dashboard but am not able to connect. Do I need to open the specific port on the ingress SG? @brandoconnor

[brandonjbjelland]

@dperic123 - It's difficult to help when I can't see what your code looks like and I don't know what you tried when troubleshooting. This module aims to get you to the point where a worker cluster is live and connected to a live EKS control plane with any configuration needed to communicate to that cluster local. It sounds like you've reached this point but you're struggling to get further in connecting to the dashboard service.

AWS has good docs on how to get you this far. By your description, it sounds like you don't have the dashboard proxy up. Read up on that link and comment back (with code samples and what was tried) if you've gone through those docs and still see trouble. I'm sure you can make it go! 💨

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.