Amazon EC2 Container Service vs Quay.io: What are the differences?
Amazon EC2 Container Service: 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; Quay.io: Secure hosting for private Docker repositories. Simply upload your Dockerfile (and any additional files it needs) and we'll build your Dockerfile into an image and push it to your repository.
Amazon EC2 Container Service belongs to "Containers as a Service" category of the tech stack, while Quay.io can be primarily classified under "Docker Registry".
Some of the features offered by Amazon EC2 Container Service are:
- Docker Compatibility
- Managed Clusters
- Programmatic Control
On the other hand, Quay.io provides the following key features:
- Secure - Your data is transferred using SSL at all times and encrypted when at rest. More information available in our security guide
- Shareable - Have to share a repository? No problem! Share with anyone you choose
- Cloud Hosted - Accessible from anywhere, anytime
"Backed by amazon" is the top reason why over 97 developers like Amazon EC2 Container Service, while over 2 developers mention "Great UI" as the leading cause for choosing Quay.io.
What is Amazon EC2 Container Service?
What is Quay.io?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Amazon EC2 Container Service?
What are the cons of using Quay.io?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
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.
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) )
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.
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.
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.
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.