AWS EKS Deployment¶

Orion deploys on AWS EKS using EKSCTL for automated cluster provisioning. Juno provides an EKS Deployment repo as the canonical starting point — the SETUP.md there is the authoritative step-by-step installation guide.
Prerequisites: Complete the EKS Prerequisites guide before starting.
Total deployment time: ~1.5 hours (30–45 min prerequisites + 20–30 min cluster + Orion install)
Deployment Steps¶
Follow the SETUP.md in the EKS Deployment repo. It walks through:
- Customizing
examples/eks.yaml(cluster name, region, AZs, instance types) - Running
eksctl create cluster(~15 minutes) - Optionally adding Karpenter for cost-optimized dynamic node provisioning
- Installing ArgoCD to provide a visual management dashboard
- Configuring
ingress-nginxwith NLB subnet configuration - DNS and TLS setup
- Deploying Orion via the Juno one-click installer (Helm)
What Gets Deployed¶
| Resource | Description |
|---|---|
| Amazon EKS Cluster | Managed Kubernetes control plane |
| Managed Node Groups | Initial worker nodes (CPU and/or GPU) |
| VPC | Public and private subnets, NAT Gateway |
| Karpenter | Optional dynamic node autoscaling |
| NGINX Ingress | Traffic routing via pre-configured NLB |
IAM Roles (Created Automatically by EKSCTL)¶
| Role | Managed Policies |
|---|---|
| EKS Cluster Service Role | AmazonEKSClusterPolicy |
| Node Group Instance Role | AmazonEKSWorkerNodePolicy, AmazonEKS_CNI_Policy, AmazonEC2ContainerRegistryReadOnly |
| Load Balancer Controller Role | AWS Load Balancer Controller policy |
| Cluster Autoscaler Role | Auto Scaling Group management |
| EBS CSI Driver Role | AmazonEBSCSIDriverPolicy |
For detailed IAM policy definitions and security configuration, see the Security Guide.
Reconnecting to an Existing Cluster¶
Use your AWS credentials and the kubeconfig generated during cluster creation. Refer to the SETUP.md for the reconnect steps.
Support¶
- Technical: support@juno-innovations.com
- Sales & Licensing: sales@juno-innovations.com
- Community: Discord