How to connect to EKS Cluster?

1. Keep the AWS credentials such as Access Key and Secret Access Key used in Applications Manager Amazon monitor ready.
   
2. Login using the AWS credentials by executing the below command and entering the relevant details. Make sure to provide the proper region name of the EKS cluster: 
   
   

   aws configure
3. Create the KUBECONFIG file for the required cluster using the below command:  
   aws eks --region {REGION} update-kubeconfig --name {CLUSTER_NAME} --kubeconfig {FILEPATH}
   
   In the above command,
1. replace {REGION} with the region of the EKS cluster
   
2. replace {CLUSTER_NAME} with the EKS cluster name
   
3. replace {FILEPATH} with the path where the KUBECONFIG file should be created. 
   
   Example: aws eks --region us-east-1 update-kubeconfig --name EKS-CLUSTER --kubeconfig /home/user/kubeconfig
1. 

   Note: The current user (running the commands) should have the permission to create and access the KUBECONFIG file.
4. Execute the below commands to verify if the user is able to access the EKS cluster, replace <FILEPATH> with the path where the KUBECONFIG file should be created:
   
1. kubectl get nodes --kubeconfig <FILEPATH>
2. kubectl get pods -A --kubeconfig <FILEPATH>
5. If any error occurs, refer the Possible Errors in EKS Monitor and their troubleshooting section and implement necessary steps.
   

1. If you are using a private EKS endpoint and you encounter this error, refer here to run kubectl commands using private endpoint access.
   

1. If you want to add access to kubernetes API server for a specific IP address alone, refer here.
   

2. Ensure that the DNS hostnames are enabled in VPC of the EKS Cluster. To enable DNS hostnames and DNS resolution, refer here.

3. Ensure if the security group's inbound policy is properly configured.

1. Ensure that the user whose credentials were used to add the EKS monitor has root permissions.

2. To resolve unauthorized error, refer here.

3. To add an IAM user to enable access to EKS cluster, refer here.
   

1. Increase the timeout value. (The default and minimum value for timeout is 30 seconds). To increase the value, go to EKS monitor page, monitor actions -> Edit monitor -> give the appropriate value and update.
   

2. Ensure your system has a stable network connectivity.

3. Run the following kubectl commands to get to know the approximate amount of time it takes to receive a response as these commands take.
   

1. kubectl get nodes
   

2. kubectl get pods --all-namespaces

1. aws configure set aws_access_key_id {access_key}
2. aws configure set aws_secret_access_key {secret_access_key}
   
3. aws configure set default.region {region}
   
4. aws eks --region {region} update-kubeconfig --name {cluster_name} --kubeconfig <FILEPATH>