EKS administration

Once your EKS cluster is running, you can manage it from your own machine. View cluster resources in the AWS Console, configure local kubectl access, shell into pods, port-forward applications, and grant your apps access to other AWS resources.

View EKS resources from the AWS Console

To view EKS resources directly from the AWS Console:

1. In the Microtica console, choose the Kubernetes resource and copy the EKSConsoleRoleName output parameter value.

2. In the AWS Console header menu, choose Switch role.

   

3. Enter your Account ID, the Role name you copied from the Microtica console, and choose a Display Name for the role.

   

4. You're redirected to the AWS Console. Navigate to EKS, choose a cluster, and view all resources for the cluster directly in the AWS Console.

Set up local access to your Kubernetes cluster

To access the Kubernetes cluster, first obtain the credentials from the AWS Console.

1. Go to the AWS Console and navigate to AWS Secrets Manager.
2. Under "Secret Value," click "Retrieve Secret Value" to access the Kubernetes credentials.

Next, configure a new cluster using the kubectl utility:

1. Open your terminal or command prompt.
2. Make sure the kubectl utility is installed and configured to access your cluster.
3. Use the following commands as a template, replacing the placeholder values with your actual secret information:

export CLUSTER_NAME="<name of the cluster>" && \
export ENDPOINT="<endpoint>" && \
export API_TOKEN="<apiToken>"

kubectl config set-cluster $CLUSTER_NAME --server=$ENDPOINT --insecure-skip-tls-verify=true && \
kubectl config set-credentials $CLUSTER_NAME --token=$API_TOKEN && \
kubectl config set-context $CLUSTER_NAME --cluster=$CLUSTER_NAME --user=$CLUSTER_NAME && \
kubectl config use-context $CLUSTER_NAME

Shell into a running container

To log in to a specific pod deployed in the Kubernetes cluster, run these commands in your terminal:

# List all pods in 'microtica' namespace. Replace the namespace if you deployed the service in namespace other then the default 'microtica' namespace.
kubectl get pods -n microtica

# Choose the pod you want to login into
kubectl exec -it <pod name> sh -n microtica

Access applications in a cluster

To interact with an application running inside a Kubernetes cluster from your local environment, run these commands in your terminal:

# List all pods in 'microtica' namespace. Replace the namespace if you deployed the service in namespace other then the default 'microtica' namespace.
kubectl get pods -n microtica

# Choose the pod you want to access into
kubectl port-forward <pod name> <local port>:<container port>

Grant applications access to AWS resources

By default, the EKS cluster is set up with minimal permissions to AWS resources, prioritizing security.

Often, applications running inside the cluster need access to specific AWS resources such as SES, SQS, SNS, and Cognito to operate.

To extend the default permissions:

1. Open the AWS Console.
2. Navigate to the IAM service.
3. In the IAM dashboard, search for the "NodeInstanceRole" role linked to your EKS cluster.
4. In the role details, open the "Add Permissions" dropdown menu.
5. From the dropdown, choose "Attach Policies".
6. Browse and choose the policy that grants the permissions your apps need for the AWS resources.
7. After selecting the policy, click "Add permissions" to apply the changes.

This grants your applications the access they need to AWS resources while keeping your EKS cluster secure.

Next steps

• Amazon EKS template overview
• Connect an existing Kubernetes cluster