Test the Cluster

Configure IAM authentication for the cluster:

You will likely see an error in the output similar to this:

[✖]  neither aws-iam-authenticator nor heptio-authenticator-aws are installed
[ℹ]  cluster should be functional despite missing (or misconfigured) client binaries
[✔]  EKS cluster "eksworkshop-eksctl" in "us-east-2" region is ready

This is caused by eksctl wanting to use aws-iam-authencator to pull IAM tokens. As of aws-cli version 1.16.156, this token functionality is built in. Let’s check our aws-cli version:

aws --version # in Cloud9, the version output should already be higher than 1.16.156

Your Cloud9 workspace should already have a version late enough to pull IAM tokens.

If you need to update the aws-cli, use this command:

pip install awscli --upgrade --user # this updates aws-cli to the latest available version for the user

aws --version

We can update our kubectl config file to use the aws-cli for pulling IAM tokens with this command:

aws eks update-kubeconfig --name eksworkshop-eksctl # this updates kubeconfig to pull iam tokens using aws-cli

Test the cluster:

Confirm your Nodes:

kubectl get nodes # if we see our 3 nodes, we know we have authenticated correctly

Export the Worker Role Name for use throughout the workshop

STACK_NAME=$(eksctl get nodegroup --cluster eksworkshop-eksctl -o json | jq -r '.[].StackName')
INSTANCE_PROFILE_ARN=$(aws cloudformation describe-stacks --stack-name $STACK_NAME | jq -r '.Stacks[].Outputs[] | select(.OutputKey=="InstanceProfileARN") | .OutputValue')
ROLE_NAME=$(aws cloudformation describe-stacks --stack-name $STACK_NAME | jq -r '.Stacks[].Outputs[] | select(.OutputKey=="InstanceRoleARN") | .OutputValue' | cut -f2 -d/)
echo "export ROLE_NAME=${ROLE_NAME}" >> ~/.bash_profile
echo "export INSTANCE_PROFILE_ARN=${INSTANCE_PROFILE_ARN}" >> ~/.bash_profile


You now have a fully working Amazon EKS Cluster that is ready to use!