AWS Fargate Customers

One of the benefits that we see with AWS is our teams don't have to focus as much on the infrastructure, and therefore are able to focus on development, and focus on the customer. So, with Delays and Cancels, I think we came up with the idea and took it all the way to implementation in less than 60 days.

AWS Serverless helps us scale reliably week to week as we move from event to event. Each event brings its own set of complexities from size and scale, and what we need to do. Serverless really allows us the speed, the agility, and the reliability to do that each week.

Serverless has allowed us to simplify our infrastructure, making it easier for our teams to innovate and deliver value.

Amazon ECS with AWS Fargate has been the perfect combination for us. AWS Fargate integrates well with other AWS services with almost zero maintenance.

We’ve improved velocity, achieved efficiencies, and refactored our architecture by migrating from an on-premises architecture to Amazon ECS with AWS Fargate.

Using AWS, we can update, improve, and introduce new capabilities on a daily basis without making major software releases.

The success of this migration showed that Fargate is a great choice for customer facing Prime Video services, and we’re seeing many other teams choose Fargate for their services.

Our infrastructure has been largely on autopilot. Using Amazon ECS definitely saves a lot of time for us.”

All of our Amazon ECS instances use AWS Fargate, which takes off a huge piece of overhead. As a fast-scaling startup, that’s exactly what we need.

We chose the solution of Amazon ECS and AWS Fargate for a variety of reasons: It’s a fully distributed architecture, it enable DevSecOps patterns, was backwards compatible with our legacy container orchestration platform, is fully automated and automatable, is secure by default, is cost effective, and enables NoOps patterns.

Our engineering team began migrating all of our systems to AWS Fargate. Because AWS Fargate exposed the same APIs and endpoints that Amazon ECS did, the migration experience was extremely smooth and we immediately experienced improvements in operational efficiency. Before AWS Fargate, Samsung typically had administrators and operators dedicated to managing web services for the Samsung developer portal. However, as we migrated to AWS Fargate, we were able to easily eliminate the need for an administrator, saving operational costs while improving development efficiency. Now, our operations and administration teams are focused more on elaborate logging and monitoring activities, further improving overall service reliability, security, and performance.

At Vodafone Digital UK, we initially built our service containers to run on AWS using the Amazon ECS orchestration layer on Amazon EC2. Once our platform started growing and experiencing scaling challenges, the Digital Architects looked at AWS Fargate to mitigate the growing pains and improve our platform stability. Once the technology had matured and price cuts were announced in January 2019, the Digital Architects defined a plan to migrate our Services from Amazon EC2 to AWS Fargate while keeping the familiar Amazon ECS orchestration layer, and the first Story on the Digital backlog for this piece of work was born. We are now halfway through the migration plan with the middleware of our My Vodafone App, one of our key services, being amont the latest ones to make the jump. Furthermore, all the new Digital Services and Channels are deployed on AWS Fargate by default. Serverless deployments still need to be properly planned, optimized, and managed. However, by removing the complexity of infrastructure management and shifting some responsibilities like OS hardening and patching onto AWS, we can reduce the amount of resources we spend on these tasks and instead focus on adding value to our Vodafone customers.

As we modernize our stack with Amazon EKS, we are always looking for opportunities to increase our security posture and lessen our administrative burden. We're excited by the potential for AWS Fargate and Amazon EKS to provide out of the box isolation and ensure a secure compute environment for our applications with the highest level of security requirements. In addition, the ability to right size portions of our compute consumption, ensuring optimal utilization without having to spend cycles on capacity planning or operational overhead, is extremely compelling. This is without a doubt the most exciting Kubernetes announcement of the year.

We are using AWS Fargate to manage our containers. This allows us to delegate the scalability to the AWS platform. We’ve had some campaigns that have brought more than 100,000 users in two days, which means an increase of 50 times the traffic that our platform was receiving. The service was not affected thanks to these managed services.

In the long term, we felt that containers would make it easier for us to deploy the engine everywhere, even at scale. Engineers use AWS Fargate with Amazon ECS to automate deployment of containerized services, including clusters on virtual machines. We really love this serverless concept because it requires minimal operations maintenance.

Deploying tasks in AWS Fargate has saved us immeasurable hours when compared to our previous setup with Amazon EC2 which was tediously slow, and the ability to rollback almost instantaneously has given us the freedom to fail faster. By introducing AWS’s serverless solutions for containers, we now have the breathing room to be proactive in our day-to-day and have been able to start investing our time in END.’s Continuous Integration and Deployment processes.

We have a real time and on-demand system. We have thousands of Amazon EC2 instances running; we have AWS Fargate instances running, sending logs into Cloudwatch. We pull those logs and we push them into our Kinesis stream for processing.

Enterprise IT helped a large airline to run hundreds of complex machine learning predictions every day using containers and AWS Fargate. This allows the airline to meet their daily deadlines for data availability by running hundreds of R scripts inside of containers. This solution scales up during the morning processing window and is completely shut down outside of that, meaning the airline pays only for the processing they require - which would be extremely difficult to achieve on an equivalent on-premises infrastructure.

We started Klook with a vision to be the global leader in travel experiences, and we have always kept our technology solutions as streamlined as possible. Klook has also adapted the AWS approach to DevOps and software development, authorizing each team to move fast and release new ideas. Amazon ECS and AWS Fargate automatically balance team Docker resources, providing easy scalability. As a result, Klook has a highly secure platform that offloads a majority of its security defense and compliance certification.

The company wanted to migrate away from managing underlying infrastructure and needed to scale quickly, schedule multi-cluster workloads, and possess network-level control, and is now all in on AWS. Product Hunt’s website is architected as microservices and was developed using Ruby on Rails with a GraphQL backend and Node.js frontend. The company uses AWS Fargate to run its containers without managing servers or clusters and has been able to scale AWS Fargate to run 25 tasks at baseline in production. We moved to AWS Fargate because we need the ability to scale quickly up from baseline, run multi-container workloads, and get fine-grained network control without having to manage our own infrastructure.

The pivot to AWS Fargate was driven mainly by efficiency and to better utilize runtime and improve memory utilization. It also had the benefit of driving cost down a little bit because of the way that we were running AWS Fargate. By using a container, we were able to just allocate enough for the entire account in that container. Plus, we could make more efficient choices around information that we already had about those accounts.