Amazon EKS Guide — KubeBolt Docs

Authentication

IRSA (IAM Roles for Service Accounts) — recommended for in-cluster deployment
Pod Identity — newer EKS authentication method, also supported
AWS CLI — for local/Docker deployment, mount ~/.aws with active SSO session

Docker Compose

The compose file already mounts ~/.aws for EKS token generation. Ensure your AWS profile/SSO session is active:

kubectl config use-context my-eks-cluster
cd deploy && docker compose up -d

Helm with ALB Ingress

helm install kubebolt \
  oci://ghcr.io/clm-cloud-solutions/kubebolt/helm/kubebolt \
  --set ingress.enabled=true \
  --set ingress.className=alb \
  --set ingress.host=kubebolt.example.com

EKS Fargate is compatible with the kubeconfig mode — no DaemonSets required. (The optional agent’s DaemonSet mode needs EC2 nodes; the promread Deployment mode works anywhere.)

Amazon Managed Prometheus (AMP)

If your metrics already live in AMP, you don’t need a second pipeline: deploy the agent in promread mode and it reads the cost and workload metric families straight from your workspace, authenticating with AWS SigV4 (IRSA supported). Configure it from the Add Cluster wizard — see Connecting clusters and Metrics.