Skip to main content
Version: 1.10.0

Installing Epinio on EKS

To install on Elastic Kubernetes Service (EKS) this How-to uses these versions:

Additional requirements for EKS v1.23 and v1.24
  • Since EKS v1.23 you need to configure and install an out-of-tree AWS EBS CSI driver add-on into your EKS cluster. Please refer to this EKS documentation for details.

  • Since EKS v1.24 you need to explicitly allow pulling Epinio's app container images from its internal HTTP registry. This is due to the removal of dockershim CRI support and its replacement by containerd, which supports only trusted HTTPS registries by default. This configuration is needed on all EKS nodes before deploying an Epinio app:

    mkdir -p /etc/containerd/certs.d/
    cat > /etc/containerd/certs.d/ <<EOF
    server = ""

    capabilities = ["pull"]

    Rather than doing this manually, it's easier to apply this manifest. This does the node configuration for you. You need to edit the manifest to use the correct node count for your cluster.


Create EKS Kubernetes cluster

You need to run aws configure before proceeding with the steps below.

eksctl create cluster \
--name=<cluster-name> \
--region=us-west-1 \
--nodes=2 \
--node-type=t3.xlarge \
--node-volume-size=40 \
--managed \

Once the EKS cluster is deployed, try to access the cluster:

export KUBECONFIG=$PWD/kubeconfig-eks
kubectl get nodes

Install Cert Manager

helm repo add cert-manager
helm repo update
helm install cert-manager --namespace cert-manager --create-namespace jetstack/cert-manager --set installCRDs=true --set extraArgs={--enable-certificate-owner-ref=true}

Install Nginx Ingress Controller

Add Helm repo and then install

helm repo add ingress-nginx
helm repo update
helm upgrade --install nginx ingress-nginx/ingress-nginx --namespace nginx --create-namespace --set controller.ingressClassResource.default=true

Create a CNAME DNS entry pointing to a ELB endpoint

The ELB (Elastic Load Balancer) endpoint is automatically assigned after installing ingress-nginx-controller. To get the assigned ELB endpoint in your cluster run:

kubectl get svc -n nginx nginx-ingress-nginx-controller \
-o jsonpath='{.status.loadBalancer.ingress[0].hostname}'

This returns output like:

Use that ELB endpoint value when creating the CNAME record for your DNS zone (for example, in the AWS Route53 service):

Record name: *

Test it:


You will receive the ELB endpoint value as the answer.

Install Epinio on the cluster

helm upgrade --install epinio epinio/epinio --namespace epinio \
--create-namespace --set \
--set global.tlsIssuer=letsencrypt-production \