AWS EKS with TLS Termination

We recommend using AWS NLB on EKS for best results. Classic and Application Load-balancers (CLB and ALB) aren’t likely to work. Follow these steps to self host Kubeshark on EKS, using and AWS Load Balancer, Ingress Controller with TLS termination.

  1. Install the AWS LoadBalancer Controller Add-on
  2. Install the Nginx Ingress resource and controller of type NLB

Installing the AWS LoadBalancer Controller Add-on

  1. Create an IAM policy
  2. Create an IAM role.
  3. Install the AWS Load Balancer Controller.
  4. Check everything was installed correctly.

Follow the steps in this article to install the AWS LB Controller add-on.

Download an IAM policy for the AWS Load Balancer Controller that allows it to make calls to AWS APIs on your behalf. Once downloaded, use the AWS CLI to create an IAM policy:

curl -O

aws iam create-policy --policy-name AWSLoadBalancerControllerIAMPolicy --policy-document file://iam_policy.json

Now use eksctl to create an IAM role:

eksctl create iamserviceaccount \
  --cluster=<eks-cluster-name> \
  --namespace=<aws-loadbalancer-namespace> \
  --name=aws-load-balancer-controller \
  --role-name AmazonEKSLoadBalancerControllerRole \
  --attach-policy-arn=arn:aws:iam::78......10:policy/AWSLoadBalancerControllerIAMPolicy \
  --approve \
  --region us-east-2-this-is-an-example

With the IAM policy and role, you can use Helm to install the AWS Load Balancer Controller:

helm repo add eks
helm repo update eks

helm install kubeshark-ingress eks/aws-load-balancer-controller  -n <aws-loadbalancer-namespace> \
--set clusterName=<eks-cluster-name> \
--set serviceAccount.create=false \
--set \
--set region=us-east-2-this-is-an-example \
--set vpcId=<eks-cluster-vpx-id \
--set logLevel=info \
--set replicaCount=1 \
--set cluster.dnsDomain=<fqdn for the SSL domain>

When you’re done, verify all was installed correctly:

kubectl get deployment -n <aws-loadbalancer-namespace> aws-load-balancer-controller

Results should resemble this output:

NAME                                             READY   UP-TO-DATE   AVAILABLE   AGE
<aws-loadbalancer-namespace>-aws-load-balancer-controller   1/1     1            1           40m

Installing the Nginx Ingress Resource and Controller of Type NLB

Firstly, add the Ingress resource:

kubectl apply -f

Now download the file:


Once downloaded, open in an editor and replace the following annotations: "true" arn:aws:acm:us-east-2:71.......90:certificate/73......7 "443" "external" "instance" "internet-facing"

Make sure you change the AWS Certificate Manager (ACM) ID as well: arn:aws:acm:us-east-2:71.......90:certificate/73......7

Find this line and replace with the EKS cluster’s VPC CIDR:

proxy-real-ip-cidr: XXX.XXX.XXX/XX

Deploy the edited manifest:

kubectl apply -f deploy.yaml


Use this document to troubleshoot.