aws-iam-authenticator is the Old Way

Since Sep 4 2019, the aws eks get-token command, available in AWS-CLI version 1.16.232 or greater of the AWS CLI, is alternative of :

aws-iam-authenticator token

This means, if you’ve already installed :

• kubectl
• aws CLI
• aws-iam-authenticator

You should keep kubectl and aws-cli , but you can get rid off the 3rd aws-iam-authenticator

Reference: https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html

Run in Container

The docker image “abdennour/kubectl” has two streams :

• kubectl only ( current last version : v1.14.7)
• kubectl combined with aws CLI ( current last version : v1.14.7-aws1.16.277)

# docker-compose sample
services:
  kubectl:
    image: abdennour/kubectl:v1.14.7-aws1.16.277
    volumes:
      - .:/code
      - aws-creds:/root/.aws:ro
    restart: "no"
    entrypoint: kubectl
    environment:
      AWS_PROFILE: myawsprofile
      KUBECONFIG: /code/mykubeconfig

https://hub.docker.com/r/abdennour/kubectl/tags

If you are curious to check my other images, navigate to https://hub.docker.com/u/abdennour

Bonus:

Udemy course about running EKS on production : https://www.udemy.com/course/aws-eks-kubernetes