Kubernetes on AWS
EC2 instances in your AWS account, with Kubernetes built in.
Edka provisions a Kubernetes platform on EC2 in your own AWS account: apps, databases, private networking, automations, AI agent runtimes, EBS storage, load balancers, and autoscaling across availability zones.
- Kubernetes cluster in your own AWS account
- Control plane across three availability zones
- EBS gp3 volumes and network load balancers
- Autoscaled pools on Auto Scaling groups
- Apps, deployments, and GitOps workflows
- PostgreSQL, MySQL, Valkey, ClickHouse, and backups
- Codex, Hermes, and OpenClaw agents
- Logs, metrics, diagnostics, and operational support
ACCESS // ONE IAM ROLE
Edka works through one IAM role you create with a CloudFormation stack.
The role trusts Edka only with your organization's external ID, and every role Edka creates for a cluster carries the stack's permissions boundary. SSH and the Kubernetes API are closed to the internet unless you allow networks, and every instance requires IMDSv2 and boots from an encrypted volume.
Your AWS account
The VPC, EC2 instances, EBS volumes, and load balancers live in your account, on your AWS bill, under your own policies and quotas.
Availability zones
A high availability control plane runs across three zones. Worker pools pick their zone and EC2 type, and autoscaled pools grow from zero through Auto Scaling groups.
Kubernetes native portability
Keep kubectl access, GitOps workflows, open components, and a practical detach path if your infrastructure needs change.
1. Connect the account
Create Edka's CloudFormation stack in your AWS account and paste the role ARN into Edka.
2. Provision the foundation
Pick a region, the control plane's availability, and the EC2 types. Edka creates the VPC, the instances, and the add-ons for EBS storage, load balancers, and autoscaling.
3. Run apps, data, automations, and agents
Deploy applications, databases, workflow services, and agent runtimes with GitOps, logs, metrics, backups, and rollback paths.
Create the IAM role for Edka with a CloudFormation stack.
What Edka creates in your account, storage, load balancers, autoscaling, and the NAT gateway.
Run Codex environments, Hermes, and OpenClaw inside your own Kubernetes cluster.
Run PostgreSQL, MySQL, Valkey, and ClickHouse next to your apps and automations.
Enable networking, observability, registry, storage, and automation components.
What is Edka for AWS Kubernetes?
Edka provisions Kubernetes clusters on EC2 in your own AWS account and adds workflows for apps, databases, deployments, add-ons, TLS, observability, automations, and private agent runtimes.
Does Edka use EKS?
No. Edka runs K3s on EC2 instances it creates in your account, with the control plane on its own instances. Each cluster runs the AWS cloud controller manager, the EBS CSI driver, and the AWS Load Balancer Controller.
How does Edka get access to my AWS account?
Through one IAM role you create with Edka's CloudFormation stack. The role trusts Edka only when Edka presents your organization's external ID, and every role Edka creates for a cluster carries the stack's permissions boundary. Delete the stack to remove the access.
Which AWS regions can I use?
us-east-1, us-east-2, us-west-1, us-west-2, ca-central-1, eu-central-1, eu-central-2, eu-west-1, eu-west-2, eu-west-3, eu-north-1, eu-south-1, eu-south-2, ap-south-1, ap-southeast-1, ap-southeast-2, ap-northeast-1, ap-northeast-2, ap-northeast-3, and sa-east-1.
Who pays for the AWS resources?
AWS bills the instances, volumes, Elastic IPs, load balancers, and data transfer to your account. The create form estimates the monthly cost of the instances, root volumes, and addresses at AWS on-demand prices.
Can an AWS cluster scale on its own?
Yes. An autoscaled pool scales between its minimum and maximum, from zero, through an Auto Scaling group and the cluster autoscaler.
Can I add Hetzner Metal pools to an AWS cluster?
No. Metal pools join Hetzner dedicated servers to a Hetzner cluster over a vSwitch. One organization can run clusters on Hetzner and on AWS side by side.