Alternatives to Docker for AWS logo

Alternatives to Docker for AWS

Amazon EC2 Container Service, Google Kubernetes Engine, Amazon EKS, AWS Fargate, and Azure Kubernetes Service are the most popular alternatives and competitors to Docker for AWS.
94
159
+ 1
0

What is Docker for AWS and what are its top alternatives?

An integrated, easy-to-deploy environment for building, assembling, and shipping applications on AWS, Docker for AWS is a native AWS application optimized to take optimal advantage of the underlying AWS IaaS services while giving you a modern Docker platform that you can use to deploy portable apps.
Docker for AWS is a tool in the Containers as a Service category of a tech stack.

Top Alternatives to Docker for AWS

  • Amazon EC2 Container Service
    Amazon EC2 Container Service

    Amazon EC2 Container Service lets you launch and stop container-enabled applications with simple API calls, allows you to query the state of your cluster from a centralized service, and gives you access to many familiar Amazon EC2 features like security groups, EBS volumes and IAM roles. ...

  • Google Kubernetes Engine
    Google Kubernetes Engine

    Container Engine takes care of provisioning and maintaining the underlying virtual machine cluster, scaling your application, and operational logistics like logging, monitoring, and health management. ...

  • Amazon EKS
    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. ...

  • AWS Fargate
    AWS Fargate

    AWS Fargate is a technology for Amazon ECS and EKS* that allows you to run containers without having to manage servers or clusters. With AWS Fargate, you no longer have to provision, configure, and scale clusters of virtual machines to run containers. ...

  • Azure Kubernetes Service
    Azure Kubernetes Service

    Deploy and manage containerized applications more easily with a fully managed Kubernetes service. It offers serverless Kubernetes, an integrated continuous integration and continuous delivery (CI/CD) experience, and enterprise-grade security and governance. Unite your development and operations teams on a single platform to rapidly build, deliver, and scale applications with confidence. ...

  • Hyper
    Hyper

    Hyper.sh is a secure container hosting service. What makes it different from AWS (Amazon Web Services) is that you don't start servers, but start docker images directly from Docker Hub or other registries. ...

  • Azure Container Service
    Azure Container Service

    Azure Container Service optimizes the configuration of popular open source tools and technologies specifically for Azure. You get an open solution that offers portability for both your containers and your application configuration. You select the size, the number of hosts, and choice of orchestrator tools, and Container Service handles everything else. ...

  • Docker Cloud
    Docker Cloud

    Docker Cloud is the best way to deploy and manage Dockerized applications. Docker Cloud makes it easy for new Docker users to manage and deploy the full spectrum of applications, from single container apps to distributed microservices stacks, to any cloud or on-premises infrastructure. ...

Docker for AWS alternatives & related posts

Amazon EC2 Container Service logo

Amazon EC2 Container Service

13.8K
9.9K
325
Container management service that supports Docker containers
13.8K
9.9K
+ 1
325
PROS OF AMAZON EC2 CONTAINER SERVICE
  • 100
    Backed by amazon
  • 72
    Familiar to ec2
  • 53
    Cluster based
  • 42
    Simple API
  • 26
    Iam roles
  • 7
    Scheduler
  • 7
    Cluster management
  • 7
    Programmatic Control
  • 4
    Container-enabled applications
  • 4
    Socker support
  • 2
    No additional cost
  • 1
    Easy to use and cheap
CONS OF AMAZON EC2 CONTAINER SERVICE
    Be the first to leave a con

    related Amazon EC2 Container Service posts

    Cyril Duchon-Doris

    We build a Slack app using the Bolt framework from slack https://api.slack.com/tools/bolt, a Node.js express app. It allows us to easily implement some administration features so we can easily communicate with our backend services, and we don't have to develop any frontend app since Slack block kit will do this for us. It can act as a Chatbot or handle message actions and custom slack flows for our employees.

    This app is deployed as a microservice on Amazon EC2 Container Service with AWS Fargate. It uses very little memory (and money) and can communicate easily with our backend services. Slack is connected to this app through a ALB ( AWS Elastic Load Balancing (ELB) )

    See more
    Russel Werner
    Lead Engineer at StackShare · | 7 upvotes · 479.8K 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
    Google Kubernetes Engine logo

    Google Kubernetes Engine

    1.1K
    805
    69
    Deploy, manage, and scale containerized applications on Kubernetes, powered by Google Cloud
    1.1K
    805
    + 1
    69
    PROS OF GOOGLE KUBERNETES ENGINE
    • 17
      Backed by Google
    • 17
      Powered by kubernetes
    • 12
      Docker
    • 11
      Scalable
    • 6
      Open source
    • 2
      Command line interface is intuitive
    • 2
      Decoupled app
    • 1
      Provisioning
    • 1
      Declarative management
    CONS OF GOOGLE KUBERNETES ENGINE
      Be the first to leave a con

      related Google Kubernetes Engine posts

      Emanuel Evans
      Senior Architect at Rainforest QA · | 20 upvotes · 1.5M views

      We recently moved our main applications from Heroku to Kubernetes . The 3 main driving factors behind the switch were scalability (database size limits), security (the inability to set up PostgreSQL instances in private networks), and costs (GCP is cheaper for raw computing resources).

      We prefer using managed services, so we are using Google Kubernetes Engine with Google Cloud SQL for PostgreSQL for our PostgreSQL databases and Google Cloud Memorystore for Redis . For our CI/CD pipeline, we are using CircleCI and Google Cloud Build to deploy applications managed with Helm . The new infrastructure is managed with Terraform .

      Read the blog post to go more in depth.

      See more
      Omar Mehilba
      Co-Founder and COO at Magalix · | 19 upvotes · 423.5K views

      We are hardcore Kubernetes users and contributors. We loved the automation it provides. However, as our team grew and added more clusters and microservices, capacity and resources management becomes a massive pain to us. We started suffering from a lot of outages and unexpected behavior as we promote our code from dev to production environments. Luckily we were working on our AI-powered tools to understand different dependencies, predict usage, and calculate the right resources and configurations that should be applied to our infrastructure and microservices. We dogfooded our agent (http://github.com/magalixcorp/magalix-agent) and were able to stabilize as the #autopilot continuously recovered any miscalculations we made or because of unexpected changes in workloads. We are open sourcing our agent in a few days. Check it out and let us know what you think! We run workloads on Microsoft Azure Google Kubernetes Engine and Amazon EC2 and we're all about Go and Python!

      See more
      Amazon EKS logo

      Amazon EKS

      896
      464
      3
      Highly available and scalable Kubernetes service
      896
      464
      + 1
      3
      PROS OF AMAZON EKS
      • 1
        Better control
      • 1
        Possibility to log in into the pods
      • 1
        Broad package manager using helm
      CONS OF AMAZON EKS
        Be the first to leave a con

        related Amazon EKS posts

        We are looking for a centralised monitoring solution for our application deployed on Amazon EKS. We would like to monitor using metrics from Kubernetes, AWS services (NeptuneDB, AWS Elastic Load Balancing (ELB), Amazon EBS, Amazon S3, etc) and application microservice's custom metrics.

        We are expected to use around 80 microservices (not replicas). I think a total of 200-250 microservices will be there in the system with 10-12 slave nodes.

        We tried Prometheus but it looks like maintenance is a big issue. We need to manage scaling, maintaining the storage, and dealing with multiple exporters and Grafana. I felt this itself needs few dedicated resources (at least 2-3 people) to manage. Not sure if I am thinking in the correct direction. Please confirm.

        You mentioned Datadog and Sysdig charges per host. Does it charge per slave node?

        See more
        Sebastian Gębski

        Heroku was a decent choice to start a business, but at some point our platform was too big, too complex & too heterogenic, so Heroku started to be a constraint, not a benefit. First, we've started containerizing our apps with Docker to eliminate "works in my machine" syndrome & uniformize the environment setup. The first orchestration was composed with Docker Compose , but at some point it made sense to move it to Kubernetes. Fortunately, we've made a very good technical decision when starting our work with containers - all the container configuration & provisions HAD (since the beginning) to be done in code (Infrastructure as Code) - we've used Terraform & Ansible for that (correspondingly). This general trend of containerisation was accompanied by another, parallel & equally big project: migrating environments from Heroku to AWS: using Amazon EC2 , Amazon EKS, Amazon S3 & Amazon RDS.

        See more
        AWS Fargate logo

        AWS Fargate

        580
        396
        0
        Run Containers Without Managing Infrastructure
        580
        396
        + 1
        0
        PROS OF AWS FARGATE
          Be the first to leave a pro
          CONS OF AWS FARGATE
          • 2
            Expensive

          related AWS Fargate posts

          Cyril Duchon-Doris

          We build a Slack app using the Bolt framework from slack https://api.slack.com/tools/bolt, a Node.js express app. It allows us to easily implement some administration features so we can easily communicate with our backend services, and we don't have to develop any frontend app since Slack block kit will do this for us. It can act as a Chatbot or handle message actions and custom slack flows for our employees.

          This app is deployed as a microservice on Amazon EC2 Container Service with AWS Fargate. It uses very little memory (and money) and can communicate easily with our backend services. Slack is connected to this app through a ALB ( AWS Elastic Load Balancing (ELB) )

          See more
          Azure Kubernetes Service logo

          Azure Kubernetes Service

          383
          341
          0
          Simplify Kubernetes management, deployment, and operations.
          383
          341
          + 1
          0
          PROS OF AZURE KUBERNETES SERVICE
            Be the first to leave a pro
            CONS OF AZURE KUBERNETES SERVICE
              Be the first to leave a con

              related Azure Kubernetes Service posts

              Farzad Jalali
              Senior Software Architect at BerryWorld · | 8 upvotes · 249.4K views

              Visual Studio Azure DevOps Azure Functions Azure Websites #Azure #AzureKeyVault #AzureAD #AzureApps

              #Azure Cloud Since Amazon is potentially our competitor then we need a different cloud vendor, also our programmers are microsoft oriented so the choose were obviously #Azure for us.

              Azure DevOps Because we need to be able to develop a neww pipeline into Azure environment ina few minutes.

              Azure Kubernetes Service We already in #Azure , also need to use K8s , so let's use AKS as it's a manged Kubernetes in the #Azure

              See more
              Hyper logo

              Hyper

              160
              76
              0
              On-Demand Container, Per-Second Billing
              160
              76
              + 1
              0
              PROS OF HYPER
                Be the first to leave a pro
                CONS OF HYPER
                  Be the first to leave a con

                  related Hyper posts

                  Azure Container Service logo

                  Azure Container Service

                  92
                  212
                  11
                  Deploy and manage containers using the tools you choose
                  92
                  212
                  + 1
                  11
                  PROS OF AZURE CONTAINER SERVICE
                  • 6
                    Easy to setup, very agnostic
                  • 3
                    It supports Kubernetes, Mesos DC/OS and Docker Swarm
                  • 2
                    It has a nice command line interface (CLI) tool
                  CONS OF AZURE CONTAINER SERVICE
                    Be the first to leave a con

                    related Azure Container Service posts

                    Docker Cloud logo

                    Docker Cloud

                    78
                    127
                    11
                    A hosted service for Docker container management and deployment
                    78
                    127
                    + 1
                    11
                    PROS OF DOCKER CLOUD
                    • 9
                      Easy to use
                    • 2
                      Seamless transition from docker compose
                    CONS OF DOCKER CLOUD
                      Be the first to leave a con

                      related Docker Cloud posts