Skip to main content

Accessing the IDE

As part of the lab environment, you have access to an AWS Cloud9 IDE.

To access the Cloud9 IDE, log into your AWS console and search for Cloud9 in the menu bar at the top of the screen:

Search for the Cloud9 service

When the main Cloud9 screen opens, expand the menu on the left side of the screen:

Access Cloud9 service menu

There will be a Cloud9 environment named eks-upgrades-workshop available. Click the Open button to launch the IDE:

Open the Cloud9 IDE

tip

If you do not see the eks-upgrades-workshop Cloud9 environment, this is because it is owned by another IAM user. Change the owner on Cloud9 Console.

Once the IDE has loaded, we recommend you use the + button and select New Terminal to open a new full screen terminal window.

Open new Cloud9 terminal

This will open a new tab with a fresh terminal.

info

You might see the following message: An error occurred (AccessDeniedException) when calling the UpdateEnvironment operation: User: arn:aws:sts::xxxxxxxxxx:assumed-role/eks-upgrades-admin/i-xxxxxxxxxxx is not authorized to perform: cloud9:UpdateEnvironment on resource: xxxxxxxx with an explicit deny in an identity-based policy

This is because we are disabling AWS temporary credentials. You can ignore it and move on

Shows new Cloud9 terminal

You may also close the small terminal at the bottom if you wish.

Your IDE comes pre-configured to access the workshop EKS cluster and also provides a set of tools you will need, like the aws and kubectl, pluto, eksctl, kubent CLI tools.

kubectl version
pluto version
eksctl version
kubent version
aws --version
kubent --version

Along with the Cloud9 instance, this workshop already has provisioned for you all needed resources, including the Amazon EKS cluster. Check that by running the follow command.

kubectl get nodes

You should see the following output:

NAME                                                 STATUS   ROLES    AGE   VERSION
fargate-ip-10-35-28-31.us-east-2.compute.internal    Ready    <none>   53m   v1.25.12-eks-51bfe41
fargate-ip-10-35-37-141.us-east-2.compute.internal   Ready    <none>   53m   v1.25.12-eks-51bfe41
fargate-ip-10-35-38-76.us-east-2.compute.internal    Ready    <none>   53m   v1.25.12-eks-51bfe41
fargate-ip-10-35-45-68.us-east-2.compute.internal    Ready    <none>   53m   v1.25.12-eks-51bfe41