# Validate Cluster Connectivity

Before validating the EKS Cluster Connectivity, make sure the kubeconfig file is configured in the local machine. Follow these steps to configure kubeconfig file.

* [Configure kubeconfig for public or public/private access point](https://help.gopaddle.io/overview/register-a-cluster/register-aws-eks-cluster/eks-cluster-with-public-or-public-private-access-point)
* [Configure kubeconfig for private only access point](https://help.gopaddle.io/overview/register-a-cluster/register-aws-eks-cluster/eks-cluster-with-private-access-endpoint-and-a-bastion-host)

 Check the EKS  Cluster connectivity by executing the command below

```sh
kubectl cluster-info
Kubernetes control plane is running at https://localhost:9444
CoreDNS is running at https://localhost:9444/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
```

## Troubleshoot Cluster Connectivity

1. If the cluster-info command fails, to debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
2. If the *cluster-info* command fails with the below error make sure the INBOUND access to port 443 from the Bastion Host Security Group is open in the Additional Security Group of the EKS cluster.

   ```
   W1213 13:04:18.835859   17344 transport.go:243] Unable to cancel request for *exec.roundTripper
   I1213 13:04:18.835992   17344 versioner.go:56] Remote kubernetes server unreachable
   ```

Edit the Additional Security Group in the EKS Network Configuration.

<figure><img src="https://downloads.intercomcdn.com/i/o/634569279/31c84ef8fd4df67c1cf8294e/Screen+Shot+2022-12-13+at+1.20.33+PM.png" alt=""><figcaption></figcaption></figure>

Add the INBOUND Access to the Bastion Host Security Group

<figure><img src="https://downloads.intercomcdn.com/i/o/634570616/c074e4c779606c44bdce233c/Screen+Shot+2022-12-13+at+1.40.22+PM.png" alt=""><figcaption></figcaption></figure>