EKS Prerequisites¶
Please complete the following steps before starting your EKS Deployment. The SETUP.md in the EKS Deployment repo provides a fully detailed, step-by-step guide on completing this — we recommend using it as your source of truth throughout the process.
Architecture Selection¶
Choose your deployment architecture up front — it affects your eks.yaml configuration. See the Architecture Reference for VPC layouts and a full decision matrix.
| Architecture | Security | Cost | High Availability | Best For |
|---|---|---|---|---|
| Private Single AZ | Highest | Medium | No | Compliance, high-security, dev |
| Public Single AZ | Medium | Lowest | No | Dev, testing, PoC |
| Public Multi-AZ | High | Highest | Yes | Production, enterprise |
Required Tools¶
| Tool | Purpose |
|---|---|
eksctl |
EKS cluster provisioning |
kubectl |
Kubernetes CLI |
aws-iam-authenticator |
AWS auth for kubectl |
AWS Account¶
- AWS account with
PowerUserAccess(or equivalent) - AWS CLI configured (
aws configure) - Access to: EKS, EC2, VPC, IAM, EBS, ELB, Route 53
- Service quotas sufficient for your target region and instance types — see AWS service limits
DNS & Certificates¶
- Registered domain with DNS management access
- Route 53 hosted zone recommended for AWS-native integration
- Plan your subdomain structure:
genesis.yourcompany.com→ Genesis UI,<project>.yourcompany.com→ project deployments - TLS: certbot for PoC, or cert-manager + ExternalDNS for production
Orion License¶
Contact sales@juno-innovations.com to obtain a license or arrange a trial before deploying.
Pre-Deployment Checklist¶
- eksctl, kubectl, and AWS CLI installed and configured
- AWS account permissions confirmed (
PowerUserAccessor equivalent) - Domain registered and hosted zone created
- Orion license obtained
- Architecture selected (see table above)
- Instance types and region decided — see Cost & Sizing
- Monitoring platform identified (CloudWatch, Prometheus, or compatible stack)