Amazon EKS vs Kubernetes

Need advice about which tool to choose?Ask the StackShare community!

Amazon EKS

916
476
+ 1
3
Kubernetes

59K
51K
+ 1
677
Add tool

Amazon EKS vs Kubernetes: What are the differences?

Introduction

This Markdown code provides a comparison between Amazon EKS (Elastic Kubernetes Service) and Kubernetes. It outlines the key differences between these two container orchestration platforms.

  1. Compute Resources Management: In Amazon EKS, the user does not have to worry about the underlying infrastructure management as it is handled by AWS. Kubernetes, on the other hand, requires manual configuration and management of compute resources, which can be complex and time-consuming.

  2. Cluster Management: Amazon EKS simplifies cluster management as it automatically sets up and manages the Kubernetes control plane, including updates and patches. With Kubernetes, the user is responsible for managing the control plane themselves, including upgrading and applying security patches.

  3. Integration with AWS Services: Amazon EKS seamlessly integrates with other AWS services, allowing for easy integration and consumption of services like EC2, RDS, and VPC. Kubernetes, being a platform-agnostic solution, requires additional configuration and setup to integrate with AWS services, which can be more complex.

  4. High Availability and Scalability: Amazon EKS provides built-in high availability, automatically distributing worker nodes across multiple availability zones to ensure fault tolerance. Kubernetes requires manual setup and configuration for achieving high availability and scalability, which can be more time-consuming and error-prone.

  5. Managed Control Plane Updates: Amazon EKS manages the Kubernetes control plane updates, ensuring the latest security patches and functionality updates are automatically applied. Kubernetes users need to manually upgrade the control plane to benefit from new features and security patches, which can be challenging, especially for large clusters.

  6. Pricing: Amazon EKS is a managed service, and users pay for the AWS resources they consume along with a per-hour fee for each Amazon EKS cluster. Kubernetes, being an open-source solution, is free to use, but organizations may incur costs for hardware infrastructure, maintenance, and management.

In summary, Amazon EKS offers simplified management, seamless integration with AWS services, built-in high availability, and automatic control plane updates. In contrast, Kubernetes requires more manual configuration and management, additional setup to integrate with AWS services, and manual control plane upgrades. Amazon EKS also comes at a cost as a managed service, while Kubernetes is open-source and free to use.

Decisions about Amazon EKS and Kubernetes
Andres Paredes
Lead Senior Software Engineer at InTouch Technology · | 3 upvotes · 84.6K views

If you want to integrate your cluster and control end to end your pipeline with AWS tools like ECR and Code Pipeline your best option is ECS using a EC2 instance. There are pros and cons but it's easier to integrate using cloud formation templates and visual UI for approvals, etc. ECS is free, you need to pay only for the EC2 instance but unfortunately, it is not standard then you cannot use standard tools to see and manage your Kubernetes. EKS in the other hand uses standard Kubernates definitions but you need to pay for the service and also for the EC2 instance(s) you have in your cluster.

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 9.3M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Russel Werner
Lead Engineer at StackShare · | 7 upvotes · 549.2K views

We began our hosting journey, as many do, on Heroku because they make it easy to deploy your application and automate some of the routine tasks associated with deployments, etc. However, as our team grew and our product matured, our needs have outgrown Heroku. I will dive into the history and reasons for this in a future blog post.

We decided to migrate our infrastructure to Kubernetes running on Amazon EKS. Although Google Kubernetes Engine has a slightly more mature Kubernetes offering and is more user-friendly; we decided to go with EKS because we already using other AWS services (including a previous migration from Heroku Postgres to AWS RDS). We are still in the process of moving our main website workloads to EKS, however we have successfully migrate all our staging and testing PR apps to run in a staging cluster. We developed a Slack chatops application (also running in the cluster) which automates all the common tasks of spinning up and managing a production-like cluster for a pull request. This allows our engineering team to iterate quickly and safely test code in a full production environment. Helm plays a central role when deploying our staging apps into the cluster. We use CircleCI to build docker containers for each PR push, which are then published to Amazon EC2 Container Service (ECR). An upgrade-operator process watches the ECR repository for new containers and then uses Helm to rollout updates to the staging environments. All this happens automatically and makes it really easy for developers to get code onto servers quickly. The immutable and isolated nature of our staging environments means that we can do anything we want in that environment and quickly re-create or restore the environment to start over.

The next step in our journey is to migrate our production workloads to an EKS cluster and build out the CD workflows to get our containers promoted to that cluster after our QA testing is complete in our staging environments.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Amazon EKS
Pros of Kubernetes
  • 1
    Better control
  • 1
    Possibility to log in into the pods
  • 1
    Broad package manager using helm
  • 164
    Leading docker container management solution
  • 128
    Simple and powerful
  • 106
    Open source
  • 76
    Backed by google
  • 58
    The right abstractions
  • 25
    Scale services
  • 20
    Replication controller
  • 11
    Permission managment
  • 9
    Supports autoscaling
  • 8
    Cheap
  • 8
    Simple
  • 6
    Self-healing
  • 5
    No cloud platform lock-in
  • 5
    Promotes modern/good infrascture practice
  • 5
    Open, powerful, stable
  • 5
    Reliable
  • 4
    Scalable
  • 4
    Quick cloud setup
  • 3
    Cloud Agnostic
  • 3
    Captain of Container Ship
  • 3
    A self healing environment with rich metadata
  • 3
    Runs on azure
  • 3
    Backed by Red Hat
  • 3
    Custom and extensibility
  • 2
    Sfg
  • 2
    Gke
  • 2
    Everything of CaaS
  • 2
    Golang
  • 2
    Easy setup
  • 2
    Expandable

Sign up to add or upvote prosMake informed product decisions

Cons of Amazon EKS
Cons of Kubernetes
    Be the first to leave a con
    • 16
      Steep learning curve
    • 15
      Poor workflow for development
    • 8
      Orchestrates only infrastructure
    • 4
      High resource requirements for on-prem clusters
    • 2
      Too heavy for simple systems
    • 1
      Additional vendor lock-in (Docker)
    • 1
      More moving parts to secure
    • 1
      Additional Technology Overhead

    Sign up to add or upvote consMake informed product decisions

    What is Amazon EKS?

    Amazon Elastic Container Service for Kubernetes (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on AWS without needing to install and operate your own Kubernetes clusters.

    What is Kubernetes?

    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention Amazon EKS and Kubernetes as a desired skillset
    What companies use Amazon EKS?
    What companies use Kubernetes?
    See which teams inside your own company are using Amazon EKS or Kubernetes.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Amazon EKS?
    What tools integrate with Kubernetes?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Kubernetesetcd+2
    2
    1170
    Dec 8 2020 at 5:50PM

    DigitalOcean

    GitHubMySQLPostgreSQL+11
    2
    2373
    PythonDockerKubernetes+7
    3
    1111
    May 21 2020 at 12:02AM

    Rancher Labs

    KubernetesAmazon EC2Grafana+12
    5
    1500
    Apr 16 2020 at 5:34AM

    Rancher Labs

    KubernetesRancher+2
    2
    946
    What are some alternatives to Amazon EKS and Kubernetes?
    kops
    It helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters from the command line. AWS (Amazon Web Services) is currently officially supported, with GCE in beta support , and VMware vSphere in alpha, and other platforms planned.
    Rancher
    Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.
    JavaScript
    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
    Git
    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
    GitHub
    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
    See all alternatives