AWS Containers & Kubernetes

Amazon EKS

Managed Kubernetes: AWS runs the Kubernetes control plane while you run your workloads.

What is Amazon EKS?

Elastic Kubernetes Service runs the Kubernetes control plane for you across multiple availability zones. You run worker nodes on EC2, on Fargate, or let EKS Auto Mode manage them, and use standard Kubernetes tools.

Key features

  • Certified, upstream-compatible Kubernetes
  • Managed node groups, Fargate and Auto Mode
  • IAM integration for pods
  • Add-ons for networking, storage and observability
  • Works with Helm, Argo CD and other Kubernetes tools

What it is used for

  • Kubernetes-based platforms
  • Portable workloads across clouds
  • Large microservice estates

When to use it

  • You already use or want Kubernetes
  • Portable workloads across clouds
  • Large microservice platforms

When something else fits better

  • A few simple services (ECS or App Runner are simpler)
  • Teams without Kubernetes experience

How pricing works

An hourly fee per cluster for the control plane, plus the EC2, Fargate, storage and load balancers your workloads use. Prices change and differ by region; we confirm current costs for your setup before you commit.

Equivalent on Google Cloud

The closest Google Cloud service is Google Kubernetes Engine (GKE): managed Kubernetes from the company that created Kubernetes, with an Autopilot mode that manages nodes for you.

How DomainHostly helps with Amazon EKS

  • Plan: choose the right setup, size and region for your workload and budget.
  • Set up securely: configure Amazon EKS with least-privilege access, encryption and backups where they apply.
  • Migrate: move from shared hosting, your own servers or the other cloud with minimal downtime.
  • Run and optimise: monitoring, updates and regular cost reviews so you only pay for what you use.

Containers & Kubernetes: Run applications packaged as containers, with managed Kubernetes and container registries.

What to consider: Containers & Kubernetes

  • Keep images small and scanned; store them in a private registry close to where they run.
  • Choose serverless containers for a few services and Kubernetes when you run many services or need its ecosystem.
  • Set CPU and memory requests and autoscaling rules so you pay for what containers actually use.

Related services: Containers & Kubernetes