Installation Guide
Edera supports multiple deployment targets. This page provides an overview and links to the complete guides on docs.edera.dev.
Installation Paths
Choose the guide for your platform:
| Platform | Installation Guide |
|---|---|
| AWS EKS | docs.edera.dev/guides/install/eks/ |
| Google Compute Engine | docs.edera.dev/guides/install/gce/ |
| Azure Linux | docs.edera.dev/guides/install/azure/ |
| Linode | docs.edera.dev/guides/install/linode/ |
| General installer | docs.edera.dev/getting-started/ |
Overview
Regardless of platform, Edera installation follows the same pattern:
- Provision nodes with the Edera software (via AMI on AWS, or via the Edera installer on other platforms)
- Configure RuntimeClass in Kubernetes so workloads can opt in to Edera isolation
- Deploy a test workload to verify the installation
Securing a workload requires one line in your pod spec:
runtimeClassName: ederaAWS-Specific Notes
On AWS, Edera is distributed as a pre-configured AMI shared directly to your AWS account during onboarding.
Prerequisites (AWS)
- ✅ Reviewed System Requirements
- ✅ Completed the AWS Account Setup
- ✅ Verified AMI access with the AMI listing guide
- ✅ AWS CLI and kubectl installed and configured
- ✅ Terraform (recommended)
Troubleshooting (AWS)
AMI not visible:
- Verify your account is in the approved list (contact support)
- Check you are querying the correct region
- Confirm AWS CLI credentials and permissions
EKS cluster issues:
- Ensure EKS version 1.28 or later
- Verify node group uses the Edera AMI
- Check security groups and IAM roles
RuntimeClass not working:
- Verify RuntimeClass is applied:
kubectl get runtimeclass -o yaml - Check node labels and selectors
Getting Help
- Docs: docs.edera.dev
- Troubleshooting: Common Issues
- Support: support@edera.dev
When contacting support, include your platform, region or zone, cluster version, instance types, and any error messages or logs.
Last updated on