Prerequisites
Before you begin the installation, make sure you have everything you need. Missing a prerequisite at the start means troubleshooting later.
What You Need
Access & Credentials
Google Artifact Registry (GAR) Key
- This is your authentication to Edera’s container registry
- Provided by Edera when you’re ready to deploy
- You’ll receive this as a JSON key file
- Store it securely—it’s the gateway to Edera’s installation artifacts
AWS Edera AMI
- AMI image with Edera baked in for AWS environments
- Provided by Edera to specified AWS and AWS Gov accounts
Contact Edera Support
- https://customer.edera.dev - Edera customer portal for all support issues
- Email: support@edera.dev
System Access
SSH Access to Target Nodes
- You need SSH access to every node where Edera will be installed
- Root or sudo privileges required
- The installer will reboot nodes—plan accordingly
Terminal Proficiency
- Comfort with command-line operations
- Ability to run bash scripts
- Understanding of file permissions and execution
Container Runtime
The Edera installer requires one of the following:
- Docker (preferred for most environments)
- nerdctl (alternative container runtime)
The installer checks for these automatically. If neither is present, you’ll see: "no client found".
Platform-Specific Requirements
AWS EKS
- Access to Edera AMI and account ID (provided by Edera team)
- Region awareness: Edera AMIs are currently only available in:
us-west-2us-gov-west-1(AWS GovCloud US-West)
Azure Deployments
For Azure Linux deployments, additional platform-specific requirements apply. Contact Edera support for details.
Linode/Akamai
For Linode deployments, you may need additional configuration for cloud provider integration.
Kubernetes Environment (if applicable)
If you’re installing Edera into an existing Kubernetes cluster:
- Kubernetes cluster running (version 1.24+)
- kubectl access to the cluster
- Cluster admin permissions to create RuntimeClass resources
Pre-Installation Checklist
Before moving forward, verify you have:
- ✅ Your GAR key (
key.json) from Edera support - ✅ SSH access to all target nodes
- ✅ Docker or nerdctl installed on the machine running the installer
- ✅ Permissions to reboot nodes
- ✅ (AWS only) Access to Edera AMI in supported regions
- ✅ (Kubernetes) Cluster admin access and kubectl configured
What’s Next?
Everything ready? Let’s move to the actual installation process.
Up next: Edera Installer →
