One of my favorite things about AWS is that our customers are not shy about letting us know what they want. Often that feedback makes us go in multiple different directions and at other times it illuminates a clear path. The latter are especially delightful.
Customers using ECS and Fargate together are our fastest growing cohort of new container customers. A lot of that cohort is using that combination to build and run web apps and services.
For many of these customers they want to move quickly and focus on the scalability, availability, and performance of these services. We also heard similar feedback from customers using Elastic Beanstalk to run their containerized applications.
The teams combined forces and got down to work. And today we are super excited to announce AWS App Runner.
It joins AWS Batch as the second purpose-built service built on the container orchestration expertise we have built over the past 7 years and the lessons learnt from years of helping customers run web apps with Elastic Beanstalk.
App Runner focuses on ease of use and high performance, and bakes in our deployment best practices (see the Builder's Library article by @clare_liguori). Going from code or container image to running service on AWS was never easier and we're just getting started.
You can use App Runner from the console or, via AWS Copilot, which also the CLI for App Runner. Read all about AWS App Runner in the blog post: aws.amazon.com/blogs/aws/app-…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Hi folks, meet Bottlerocket, an open-source (Linux-based) operating system purpose built for hosting containers github.com/bottlerocket-o…
Bottlerocket encapsulates lessons that we (and our customers and partners) have learned over the past 5 years or so from running containers at scale. Bottlerocket focuses on security and maintainability and shines when you couple it with a container orchestrator.
One of the best parts of EC2 was that you were no longer concerned how many racks you had in your data center, where they sat, etc. You just launched instances onto capacity that AWS managed.
Modern container orchestration, especially single tenant systems essentially regressed and made that capacity a "thing" by choosing the cluster of machines a first order construct.