Amazon EKS
Deploy Meridian inside an existing Amazon Elastic Kubernetes Service cluster. This recipe covers IAM roles for service accounts, Fargate profiles, and the minimum node group topology for production workloads.
Prerequisites
- • eksctl v0.180+ or AWS CLI with cluster admin
- • kubectl context pointed at the target cluster
- • Meridian license key with EKS entitlement
- • Helm 3.13+ installed locally
IRSA Setup
Create an IAM OIDC provider and annotate the Meridian service account with the role ARN. The agent uses STS regional endpoints to assume the role — no long-lived credentials on disk.
Fargate Profile
Target the meridian namespace with a Fargate profile. The control plane and data plane agents run serverless — no node group management, no AMI patching.
Quick Install
helm repo add meridian https://charts.getnimbus.net
helm upgrade --install meridian meridian/agent \
--namespace meridian --create-namespace \
--set licenseKey=$MERIDIAN_KEY \
--set clusterName=prod-eks
Next Steps
After the Helm release settles, verify the agent heartbeat in the Meridian dashboard. For multi-cluster topologies, repeat the IRSA binding per cluster and use a unique clusterName value.