Connecting to EKS running in the private subnet of AWS VPC from your DevBox.
Follow Connecting to AWS guide.
Go to Amazon Elastic Kubernetes Service > Clusters.
Go to your DevBox and install awscli:
Download the kubectl binaries:
Install kubectl:
Check if the cluster is accessible:
Go to Amazon Elastic Kubernetes Service > Clusters > Add cluster > Create.
Enter the name of the cluster and assign a Cluster service role which has AmazonEKSClusterPolicy permission. If no role is present, create a new one with the same permission.
Click on Next. In the Networking section, choose the VPC where your bastion host is deployed and assign 2 private subnets. In Cluster endpoint access, select Private.
Configure other configurations as required and then create the cluster. After creating the cluster, go to the compute section and under Node groups click on Add node group.
Enter the name of the node group and assign a node IAM role with AmazonEC2ContainerRegistryReadOnly, AmazonEKS_CNI_Policy and AmazonEKSWorkerNodePolicy permissions. If no role is present, create a new one with the same permissions.
Configure other configurations as required and create the nodes.
Go to your DevBox and install awscli:
Download kubectl binaries:
Install kubectl:
Click on your AWS username at the top right corner and go to Security credentials. In the Access keys section, click on Create access key. Create the key and save the CSV file.
In your DevBox, use the csv credentials to configure the awscli to your account:
Check if the cluster is accessible:
``` kubectl get svc