title: "kubectl" not connecting to aws EKS cluster from my local windows workstation
body: <p>I am trying to setup aws EKS cluster and want to connect that cluster from my local windows workstation. Not able to connect that. Here are the steps i did;</p>
  
  <ol>
  <li>Create a aws service role (aws console -> IAM -> Roles -> click "Create role" -> Select AWS service role "EKS" -> give role name "eks-role-1"</li>
  <li>Create another user in IAM named "eks" for programmatic access. this will help me to connect my EKS cluster from my local windows workstation. Policy i added into it is "AmazonEKSClusterPolicy", "AmazonEKSWorkerNodePolicy", "AmazonEKSServicePolicy", "AmazonEKS_CNI_Policy".</li>
  <li>Next EKS cluster has been created with roleARN, which has been created in Step#1. Finally EKS cluster has been created in aws console.</li>
  <li>In my local windows workstation, i have download "kubectl.exe" &amp; "aws-iam-authenticator.exe" and did 'aws configure' using accesskey and token from step#2 for the user "eks". After configuring "~/.kube/config"; i ran below command and get error like this:</li>
  </ol>
  
  <hr>
  
  <pre><code>Command:kubectl.exe get svc
  </code></pre>
  
  <hr>
  
  <pre><code>output:
  could not get token: NoCredentialProviders: no valid providers in chain. Deprecated.
          For verbose messaging see aws.Config.CredentialsChainVerboseErrors
  could not get token: NoCredentialProviders: no valid providers in chain. Deprecated.
          For verbose messaging see aws.Config.CredentialsChainVerboseErrors
  could not get token: NoCredentialProviders: no valid providers in chain. Deprecated.
          For verbose messaging see aws.Config.CredentialsChainVerboseErrors
  could not get token: NoCredentialProviders: no valid providers in chain. Deprecated.
          For verbose messaging see aws.Config.CredentialsChainVerboseErrors
  could not get token: NoCredentialProviders: no valid providers in chain. Deprecated.
          For verbose messaging see aws.Config.CredentialsChainVerboseErrors
  Unable to connect to the server: getting credentials: exec: exit status 1
  </code></pre>
  
  <hr>
  
  <p>Not sure what wrong setup here. Can someone pls help? I know some of the places its saying you have to use same aws user to connect cluster (EKS). But how can i get accesskey and token for aws assign-role (step#2: eks-role-1)?</p>