Amazon EC2 Container Service聽vs聽AWS OpsWorks

Get Advice Icon

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

Amazon EC2 Container Service
Amazon EC2 Container Service

3.4K
2.1K
+ 1
324
AWS OpsWorks
AWS OpsWorks

165
84
+ 1
42
Add tool

Amazon EC2 Container Service vs AWS OpsWorks: What are the differences?

Developers describe Amazon EC2 Container Service as "Container management service that supports Docker containers". 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. On the other hand, AWS OpsWorks is detailed as "Model and manage your entire application from load balancers to databases using Chef". Start from templates for common technologies like Ruby, Node.JS, PHP, and Java, or build your own using Chef recipes to install software packages and perform any task that you can script. AWS OpsWorks can scale your application using automatic load-based or time-based scaling and maintain the health of your application by detecting failed instances and replacing them. You have full control of deployments and automation of each component .

Amazon EC2 Container Service and AWS OpsWorks are primarily classified as "Containers as a Service" and "Server Configuration and Automation" tools respectively.

Some of the features offered by Amazon EC2 Container Service are:

  • Docker Compatibility
  • Managed Clusters
  • Programmatic Control

On the other hand, AWS OpsWorks provides the following key features:

  • AWS OpsWorks lets you model the different components of your application as layers in a stack, and maps your logical architecture to a physical architecture. You can see all resources associated with your application, and their status, in one place.
  • AWS OpsWorks provides an event-driven configuration system with rich deployment tools that allow you to efficiently manage your applications over their lifetime, including support for customizable deployments, rollback, partial deployments, patch management, automatic instance scaling, and auto healing.
  • AWS OpsWorks lets you define template configurations for your entire environment in a format that you can maintain and version just like your application source code.

"Backed by amazon" is the primary reason why developers consider Amazon EC2 Container Service over the competitors, whereas "Devops" was stated as the key factor in picking AWS OpsWorks.

According to the StackShare community, Amazon EC2 Container Service has a broader approval, being mentioned in 784 company stacks & 374 developers stacks; compared to AWS OpsWorks, which is listed in 73 company stacks and 18 developer stacks.

No Stats
- No public GitHub repository available -
- No public GitHub repository available -

What is 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.

What is AWS OpsWorks?

Start from templates for common technologies like Ruby, Node.JS, PHP, and Java, or build your own using Chef recipes to install software packages and perform any task that you can script. AWS OpsWorks can scale your application using automatic load-based or time-based scaling and maintain the health of your application by detecting failed instances and replacing them. You have full control of deployments and automation of each component 
Get Advice Icon

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

Why do developers choose Amazon EC2 Container Service?
Why do developers choose AWS OpsWorks?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
      Be the first to leave a con
      What companies use Amazon EC2 Container Service?
      What companies use AWS OpsWorks?

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

      What tools integrate with Amazon EC2 Container Service?
      What tools integrate with AWS OpsWorks?

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

      What are some alternatives to Amazon EC2 Container Service and AWS OpsWorks?
      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.
      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 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 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
      Fully managed Kubernetes container orchestration service on Microsoft Azure.
      See all alternatives
      Decisions about Amazon EC2 Container Service and AWS OpsWorks
      Russel Werner
      Russel Werner
      Lead Engineer at StackShare | 0 upvotes 4.9K views
      atStackShareStackShare
      Amazon EC2 Container Service
      Amazon EC2 Container Service
      CircleCI
      CircleCI
      Helm
      Helm
      Slack
      Slack
      Google Kubernetes Engine
      Google Kubernetes Engine
      Amazon EKS
      Amazon EKS
      Kubernetes
      Kubernetes
      Heroku
      Heroku

      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
      Interest over time
      Reviews of Amazon EC2 Container Service and AWS OpsWorks
      No reviews found
      How developers use Amazon EC2 Container Service and AWS OpsWorks
      Avatar of CloudRepo
      CloudRepo uses Amazon EC2 Container ServiceAmazon EC2 Container Service

      We use the container service so that we can deploy our application services with Dockerfiles, so that we can test locally and deploy to AWS simply.

      Additionally, the ability to scale containers and have them automatically restart in case of failure is very helpful to our operations.

      Avatar of Adminout
      Adminout uses Amazon EC2 Container ServiceAmazon EC2 Container Service

      We use the EC2 registry for secure private container registration. When used in combination with I AM roles we can control customer access to repos on and individual basis.

      Avatar of SocialCops
      SocialCops uses Amazon EC2 Container ServiceAmazon EC2 Container Service

      Amazon EC2 is our primary application hosting solution. Most applications are not exposed on the internet and use a virtually private cloud to interact with each other.

      Avatar of Brandon Adams
      Brandon Adams uses Amazon EC2 Container ServiceAmazon EC2 Container Service

      With a little forethought, ECS can handle a good portion of my development stack as though it were production. 12 Factor configuration makes this a breeze.

      Avatar of Thomas Zickell
      Thomas Zickell uses Amazon EC2 Container ServiceAmazon EC2 Container Service

      I don't like AWS BUT Pagely's VPS-3 makes it work. I still use FireHost for most things

      Avatar of thanawatsenawat
      thanawatsenawat uses AWS OpsWorksAWS OpsWorks

      Automate deploy application without SMTP.

      Avatar of Hund
      Hund uses AWS OpsWorksAWS OpsWorks

      Chef server deployments.

      How much does Amazon EC2 Container Service cost?
      How much does AWS OpsWorks cost?
      Pricing unavailable
      News about AWS OpsWorks
      More news