If you’re running these labs as part of an AWS led event in Workshop Studio, you don’t need to provision anything since all the resources needed to complete all modules will be pre provisioned.
The stack sets up the following components:
You will interact with your EKS cluster using kubectl
, you need to configure your config file to recognize the cluster. This is done by updating the kubeconfig file, which stores details about cluster authentication and access.
aws eks update-kubeconfig --name ${clusterName} --region us-east-1
You should receive an output confirming your conf file was updated:
Updated context arn:aws:eks:us-east-2:<<Account_ID>>:cluster/opea-eks-cluster in /home/cloudshell-user/.kube/config
You are now ready to interact with the Kubernetes cluster using kubectl
After updating your kubeconfig, check if you can successfully connect to the cluster. A simple test is to see if you can see the nodes associated with the cluster:
kubectl get nodes
If the command is successful, you should see an output similar to this:
NAME STATUS ROLES AGE VERSION
ip-XXX-XXX-XXX-XXX.ec2.internal Ready <none> 146m v1.27.16-eks-XXXXX
You are now ready to explore the Module of your preference.