System Requirements

This page summarizes the general requirements for running Edera. For platform-specific details, see the installation guides on docs.edera.dev.

General Requirements

Edera runs as a Kubernetes RuntimeClass on supported node types. All nodes running Edera workloads must:

• Run on hardware with virtualization support (Intel VT-x or AMD-V)
• Use UEFI boot mode (required for the Xen hypervisor backend)
• Run a supported Kubernetes version (1.28 or later recommended)

Platform-Specific Requirements

Edera supports multiple deployment targets. Refer to the relevant guide for detailed requirements:

AWS-Specific Requirements

If you are deploying on AWS, Edera is distributed as a pre-configured AMI. Your AWS account must be granted access to the AMI during onboarding.

Supported Instance Types

• Recommended: M5, M5n, C5, C5n, R5 families (xlarge or larger)
• Testing: M5n.xlarge (supports ~18 default zones at 1GB per zone)
• Minimum: T3.medium (limited zone capacity)

IAM Permissions

Your AWS credentials need:

• EC2 instance management (launch, terminate, describe)
• AMI access (describe and launch from shared Edera AMIs)
• EKS cluster access (create, describe, manage node groups)
• Kubernetes RBAC, security groups, VPC access, IAM roles

Verifying AMI Access

aws ec2 describe-images \
  --owners 207567768011 \
  --query 'reverse(sort_by(Images[*].[CreationDate, ImageId, Name, State], &[0]))' \
  --output table

See the AMI listing guide for details.

Getting Help

• Account Setup (AWS): Complete your AWS account setup
• Other platforms: Contact support@edera.dev
• Technical docs: docs.edera.dev