Amazon Web Services Elastic Kubernetes Service (EKS)
Connect your account from Amazon Web Services Elastic Kubernetes Service (EKS) and Wodby will spin up a ready-to-run Kubernetes cluster for you. We will install all necessary infrastructure, so you can deploy your app using one of our stacks in a few clicks.
Specific to this provider
What Wodby sets up on Amazon EKS
Wodby creates an Amazon EKS cluster in your own AWS account from an IAM access key and a region. The network, the control plane, the add-ons, and the default node group are created for you as CloudFormation stacks.
Spread across Availability Zones
A new EKS cluster is created across multiple Availability Zones of the region you select, so the cluster does not depend on a single zone.
One load balancer for app traffic
Wodby installs the AWS Load Balancer Controller together with Envoy Gateway. A single Network Load Balancer then serves as the public entry point for all your apps.
Volumes on Elastic Block Store
Each persistent volume claim gets an EBS volume of its own. The cluster offers several storage classes to choose from, and the default class applies when you pick none.
Node types Wodby offers
The node type selector is limited to instance types that Wodby supports on EKS: x86 instances available in the selected zone, without burstable, Mac, or unsupported accelerator families. Node disk size is set at creation.
Permissions for the access key
The IAM identity behind the key needs the EC2, CloudFormation, and IAM full access policies that AWS manages, plus a short custom policy for EKS. Attach the managed policies by name; do not copy them.
Read the Amazon Web Services guide for requirements, setup steps, and limits.
Infrastructure we install and maintain
A cluster ready to run your apps
Wodby installs and connects the services for app traffic, resource monitoring, and provider integrations. Start deploying with these essentials in place, and keep them and the Kubernetes version current with Wodby.
Application routing
Publish HTTP and HTTPS endpoints for your apps. Wodby configures the gateway and routes requests to the appropriate service.
- Envoy Gateway
Know how your cluster is performing
View CPU, memory, and storage metrics in Wodby to understand resource usage and investigate capacity issues without assembling your own monitoring stack.
- Monitoring
- Node exporter
- Kubernetes state metrics
Connect to AWS load balancing
Integrate Kubernetes services with AWS load balancers through a controller installed as part of your EKS setup.
- AWS Load Balancer controller
Keep your cluster current with less manual work
Wodby upgrades its infrastructure and the infrastructure app stacks automatically, and can upgrade the Kubernetes version too, each with its own version policy and maintenance window. You choose what may change and when, and every upgrade is a task you can follow.
Automatic infrastructure upgrades
Keep Wodby's cluster networking and routing setup current. Enable automatic upgrades and choose which patch, minor, and major changes your cluster may receive.
Automatic infrastructure app updates
Update gateway, monitoring, and controller stacks automatically with their own version policy, including newer revisions of the same version.
Automatic Kubernetes upgrades
Turn automatic upgrades on and Wodby moves the cluster to new Kubernetes patch releases and keeps the VPC CNI, kube-proxy, CoreDNS, and EBS CSI driver add-ons at the AWS default, in your maintenance window. They are off by default, because each upgrade replaces the nodes and restarts every pod.
Maintenance on your schedule
Set separate weekdays, hours, and time zones for automatic infrastructure, infrastructure app, and Kubernetes upgrades, so routine maintenance starts when it suits your team.
Reviewable, traceable updates
Review infrastructure app changelogs, Kubernetes upgrade plans, and available release notes. Follow upgrade tasks, retry failed operations, and receive success or failure emails for automatic infrastructure and Kubernetes upgrades.
App environment network isolation
On supported clusters, network policies isolate incoming traffic between app environments while keeping services in the same environment connected.
Need more capacity? On supported scalable managed clusters, set minimum and maximum node counts and let the provider's autoscaler adjust capacity to workload demand. Explore cluster scaling →
How cluster updates work →Budget self-hosted Kubernetes on your own servers
Amazon Web Services offers VMs that can be used for a self-hosted Kubernetes setup, which means you can connect a VM, add more VMs as worker nodes later, and avoid the extra managed Kubernetes overhead around the control plane, cloud load balancer, and block storage. The tradeoff is no autoscaling and no high availability compared to a managed cluster, but it can be a good fit for smaller workloads and lower budgets. Read more on the self-hosted Kubernetes page.
Popular stacks
Browse common Wodby stacks and open the stack page for setup, services, integrations, and deployment options.
Prefer not to use your own cloud account or server?
If you want the Wodby Kubernetes workflow without a provider account or server of your own, deploy with Wodby Cloud. It gives you the same managed stacks and deployment model without requiring a cluster in your own cloud account or on your own server.
No separate provider account
Start deploying without creating and wiring AWS, GCP, Azure, DigitalOcean, or dedicated server infrastructure first.
Less infrastructure hassle
Wodby provides the cluster and platform foundation so your team can focus on applications instead of setting up and owning the infrastructure itself.
Simple pay-as-you-go model
Wodby Cloud pricing provides a simpler way to get started with a managed Kubernetes environment and predictable platform costs.
Deploy on Amazon Web Services Elastic Kubernetes Service (EKS) with Wodby
Launch a production-ready environment faster with Wodby-managed infrastructure, deployment workflows, and application stacks.