Q: What is AWS Fargate?

AWS Fargate is a serverless compute engine for containers that works with both Amazon Elastic Container Service (ECS) and Amazon Elastic Kubernetes Service (EKS). AWS Fargate makes it easy to focus on building your applications. Fargate eliminates the need to provision and manage servers, lets you specify and pay for resources per application, and improves security through application isolation by design.

Q: Why should I use AWS Fargate?

AWS Fargate enables you to focus on your applications. You define your application content, networking, storage, and scaling requirements. There is no provisioning, patching, cluster capacity management, or infrastructure management required.

Q: What use cases does AWS Fargate support?

AWS Fargate supports all of the common container use cases including microservices architecture applications, batch processing, machine learning applications, and migrating on-premises applications to the cloud.

Q: What is the pricing of AWS Fargate?

With AWS Fargate, you pay only for the amount of vCPU, memory, and storage resources consumed by your containerized applications.

vCPU and memory resources are calculated from the time your container images are pulled until the Amazon ECS task or EKS pod terminates, rounded up to the nearest second. A minimum charge of 1 minute applies. 20 GB of ephemeral storage is available for all Fargate Tasks and Pods by default—you only pay for any additional storage that you configure.

Fargate supports Spot and Compute Savings Plan pricing options just like with Amazon EC2 instances. You can find additional details on the pricing page.

Q: How does AWS Fargate work with Amazon ECS and Amazon EKS?

Amazon Elastic Container Service (ECS) is a highly scalable, high performance container management service that supports Docker containers and Amazon Elastic Kubernetes Service (EKS) is a fully managed Kubernetes service. Both ECS and EKS use containers provisioned by Fargate to automatically scale, load balance, and optimize container availability through managed scheduling, providing an easier way to build and operate containerized applications.

Q: How should I choose when to use AWS Fargate?  

Choose AWS Fargate for its isolation model and security. You should also select Fargate if you want to launch containers without having to provision or manage EC2 instances. If you require greater control of your EC2 instances or broader customization options, then use ECS or EKS without Fargate. Use EC2 for GPU workloads, which are not supported on Fargate today.

Q: Can I run my Arm-based applications on AWS Fargate?

Yes. AWS Fargate allows you to run your Arm-based applications by using Arm-compatible container images or multi-architecture container images in Amazon Elastic Container Registry (Amazon ECR). You can simply specify the CPU Architecture as ARM64 in your Amazon ECS Task Definition to target AWS Fargate powered by Arm-based AWS Graviton2 Processors.

Q: Why should I use AWS Fargate powered by Graviton2 processors?

AWS Graviton2 processors are custom built by Amazon Web Services using 64-bit Arm Neoverse cores to deliver the best price performance for your cloud workloads. AWS Fargate powered by AWS Graviton2 processors delivers up to 40% improved price/performance at 20% lower cost over comparable Intel x86-based Fargate for a variety of workloads such as application servers, web services, high-performance computing, and media processing. You get the same serverless benefits of AWS Fargate while optimizing performance and cost for running your containerized workloads.

Q: Can I run my Amazon ECS Windows containers on AWS Fargate?

Yes. AWS Fargate offers a serverless approach for running your Windows containers. It removes the need to provision and manage servers and lets you specify and pay for resources per application. Fargate provides task-level isolation and handles the necessary patching and updating to help provide a secure compute environment.

Can I use my existing Microsoft Windows License with AWS Fargate? 

Since Fargate is a serverless compute engine, customers do not need to manage the underlying compute instances running in Fargate. Therefore, Fargate will manage the Windows OS licenses for you and the cost of doing so is built into the Fargate pricing.

Q: Which Windows Server versions are supported with AWS Fargate?

Fargate supports Windows Server 2019 Long-Term Servicing Channel (LTSC) release on Fargate Windows Platform Version 1.0.0 or later.

Fargate vCPU-based Service Quotas

Q: What is changing?

AWS Fargate is transitioning service quotas from the current ECS task and EKS pod count based concurrent quotas to vCPU-based quotas for On-Demand and Spot usage. The new vCPU-based quotas will replace the existing tasks and pods count-based quotas. With vCPU-based quotas, we are simplifying the service quotas experience as your accounts’ usage against these quotas is now measured using vCPUs, the primary resource provisioned by your applications.

Q: How do vCPU-based quotas benefit me?

With vCPU-based quotas, Fargate uses the number of vCPUs provisioned by a task or pod as the unit that counts toward the new vCPU-based quota. You can now more easily forecast, manage, and request quotas based on the vCPUs provisioned by your applications. Currently, you manage quotas on Fargate using task and pod count, undifferentiated by vCPUs your applications need. For example, an account with service quota of 250 tasks is able to launch up to 250 0.25 vCPU or 250 4vCPU tasks. With the new vCPU-based service quotas, a quota of 1,000 vCPUs allows you to concurrently launch up to 4,000 0.25 vCPU or up to 250 4 vCPUs tasks. With vCPU-based quotas, On-Demand tasks or pods and Spot tasks usage against the vCPU quotas are measured in terms of the number of vCPUs attached to your running tasks or pods.

Q: How many On-Demand and Spot Amazon ECS tasks or Amazon EKS pods can I run on AWS Fargate?

There will be no impact to your running tasks or pods with the migration to vCPU-based quotas. Your new vCPU-based quotas can be viewed on Service Quotas Console. You can run one or more On-Demand, Spot Fargate tasks or pods in an AWS account, and the number of vCPUs assigned to the running tasks or pods accrue up to a total of vCPU quota stated, listed in the table below. If your account already has an approved quota increase, you will continue to be able to launch at least the same number of tasks or pods. Similar to current quotas, new AWS accounts may start with lower quotas than those described here and these quotas can increase over time. Fargate is constantly monitoring your usage within each region and your quotas are raised automatically based on your use of AWS.

Quotas per account per region (Up to) New vCPU-based quotas Adjustable
Fargate On-Demand vCPU resource count 4,000 vCPUs Yes
Fargate Spot vCPU resource count 4,000 vCPUs Yes

Q: When can I start using vCPU-based quotas?

Starting October 3, 2022 and ending by October 21, 2022, Fargate will automatically switch over your accounts to the new vCPU quotas in a phased manner. To help you familiarize yourself with the new vCPU quotas experience, Fargate provides you the option to opt-in to vCPU quotas starting September 8, 2022. ECS Fargate customers can do so seamlessly by using the PutAccountSettingDefault API. In addition, customers can start using vCPU quotas by filing a request in the AWS Support Center console. After the automatic switchover in October 2022, customers will still have the option to opt-out of vCPU quotas until end of October 2022 to test and remediate their systems should they face any issues. At the end of this transition period, starting November 2022, Fargate will switch all customers to vCPU quotas, regardless of customers’ account settings, and the current task and pod count-based quotas will no longer be supported after November 16, 2022. By testing and opting in earlier, you give yourself valuable time to make modifications to your limit management tools and you minimize the risk of any impact to your systems.

Q: How do I opt in and out of vCPU quotas experience?

Throughout the transition period over the coming months, you can choose to manage limits using new vCPUs-based quotas by opting-in and out seamlessly into the vCPU limits experience by using the PutAccountSettingDefault API (for ECS Fargate customers) or by filing a request with AWS Support by choosing “Create case” regarding “Service Limit Increase”. You opt in or out of the vCPU-based quotas at an AWS account level and region level. Hence, during the transition window, based on your account settings, your usage or any limit increases will be counted towards either the task and pod count-based quotas or the vCPU-based quotas. Once your request to opt-in to vCPU quotas is processed, your task and pod count’s applied limit will be marked zero on the Service Quotas Console. You can now start managing your Service Quotas using vCPU-based quotas.

Q: What if I run into issues with vCPU-based quotas?

If you run into issues with vCPU-based quotas during the transition period, you can temporarily opt out of vCPU quotas and remediate your systems. However, your account will automatically be transitioned back to vCPU quotas after October 2022. Regardless of your account settings, all AWS accounts will switch to vCPU quotas after the transition period, so it is important for you to test your systems with vCPU quotas before the transition period ends.

Q: What are the changes I should be aware of with the migration to vCPU-based quotas?

By testing and opting in to vCPU quotas earlier, you give yourself valuable time to get familiar with the new vCPU-based quotas and make modifications to your limit management tools. The below are some of the changes you should be aware of while migrating to vCPU quotas. If you have backward integration with the current quotas’ limit exceeded error, we recommend testing your systems before the transition period ends. For instance, with vCPU quotas, Fargate will return a new error message when exceeding your new vCPU quotas. For reference, new error message for On-Demand quotas: “You’ve reached the limit on the number of vCPUs you can run concurrently” and for Spot quotas: ”You’ve reached the limit on the number of vCPUs you can run as spot tasks concurrently”. We recommend reviewing your system for changes if you have integration with Service Quota’s Quota Quote, Service Quota API and templates. With Amazon CloudWatch metrics integration in Service Quotas, you can monitor Fargate usage against the new vCPU-based quotas by configuring new alarms to warn about approaching quotas.

Q: How can I request a limit increase?

You can request limit increases using the Service Quotas Console. For any AWS account, you can take the following steps to request an increase for quotas. If you have opted-in to vCPU-based quotas, you can request limit increase against vCPU-based quotas. To request a limit increase, select “Request Limit Increase” in Service Quota console, state your requirement in vCPUs, and get approved for additional vCPUs. If you continue to use task and pod count-based quotas, you can request a limit increase against the existing task and pod count quotas (current process). Should you need further assistance with the request, you can contact customer support on AWS Support Center page to follow-up on an existing case or by choosing “Create case” regarding “Service Limit Increase”.

Q: How can I view my current task and pod count-based quotas and new vCPU based-quotas?

You can find your current task and pod count quotas on the Service Quotas Console and by using the Service Quota API. During the transition period, you will be able to view both current task and pod count-based quotas and new vCPU-based quotas on Service Quotas Console.

Q: Will the migration to vCPU quotas affect running tasks and pods?

No, opting in to and out of vCPU-based quotas during this transition period will not affect any running tasks or pods.

Q: Can I still launch the same number of tasks and pods?

Yes, the vCPU-based quotas allow you to launch at least the same number of task or pods as you do today with task and pod count-based quotas. 

Q: Will I be able to view actual usage against these new quotas?

Once vCPU quotas are launched, you can track and inspect your vCPU usage against these quotas in Service Quotas. Service Quotas also enables customers to use CloudWatch for configuring new alarms to warn customers of approaching their vCPU-based quotas.

Q: What happens to my quotas if I opt out of vCPU quotas during the transition period?

If you decide to opt out during the transition period, your quotas will revert to task and pod count-based limit values you had before you opted in. Fargate will automatically switch your account to vCPU quotas after October 2022.

Q: What will happen if I take no action?

If you do not opt-in to the new vCPU quotas, you will automatically begin to see vCPU-based quotas starting October 3, 2022 as Fargate will automatically migrate your account to vCPU-based quotas.

Q: Are these vCPU-based quotas regional?

Similar to task and pod count-based quotas, vCPU-based quotas for an AWS account are on a per-region basis. 

Q: Will these new quotas have an impact on my monthly bill?

No, the new vCPU-based quotas as such will have no impact to your monthly bill.

Security and Compliance

Q: With which compliance programs does AWS Fargate conform?

AWS Fargate meets the standards for PCI DSS Level 1, ISO 9001, ISO 27001, ISO 27017, ISO 27018, SOC 1, SOC 2, SOC 3, and HIPAA eligibility.

For more information, visit our compliance pages

Q: Can I use AWS Fargate for Protected Health Information (PHI) and other HIPAA regulated workloads?

Yes. AWS Fargate is HIPAA-eligible. If you have an executed Business Associate Addendum (BAA) with AWS, you can process encrypted Protected Health Information (PHI) using Docker containers deployed onto Fargate.

For more information, please visit our page on HIPAA compliance. If you plan to process, store, or transmit PHI and do not have an executed BAA from AWS, please contact us for more information.

Q: Can I use AWS Fargate for US Government-regulated workloads or processing sensitive Controlled Unclassified Information (CUI)?

Yes. Fargate is available in AWS GovCloud (US) Regions. AWS GovCloud (US) is Amazon's isolated cloud infrastructure and services designed to address specific regulatory and compliance requirements of US Government agencies, as well as contractors, educational institutions, and other US customers that run sensitive workloads in the cloud. For a full list of AWS Regions where Fargate is available, please visit our Region table.

For more information, visit our page on AWS GovCloud.

Q: Which Windows Server versions are supported with AWS Fargate?

Fargate supports Windows Server 2019 Long-Term Servicing Channel (LTSC) release on Fargate Windows Platform Version 1.0.0 or later.

Service Level Agreement (SLA)

Q: What does the AWS Fargate SLA guarantee?

Our Compute SLA guarantees a Monthly Uptime Percentage of at least 99.99% for AWS Fargate.

Q: How do I know if I qualify for an SLA Service Credit?

You are eligible for an AWS Fargate SLA credit under the Compute SLA if more than one Availability Zone in which you are running a task, within the same region, has a Monthly Uptime Percentage of less than 99.99% during any monthly billing cycle.

For full details on all of the terms and conditions of the SLA, as well as details on how to submit a claim, please see the Compute SLA details page.

Get started using AWS Fargate

Visit the Amazon ECS console
Ready to get started?
Sign up
Have more questions?
Contact us