AWS Fargate pricing is based on several factors, including the vCPU and memory resources allocated to your containers, as well as the duration of their execution. Here are some key pricing considerations for AWS Fargate:
-
vCPU and Memory Usage: Fargate charges based on the vCPU and memory resources allocated to your containers, measured in CPU per hour and memory per hour. You are billed for the total number of vCPU and memory resources provisioned for your containers, rounded up to the nearest second.
-
Task Duration: Fargate charges based on the duration that your containers are running, measured in seconds. You are billed for the time your containers are provisioned and running, from the time they start to the time they stop or are terminated.
-
Networking: There are no additional charges for data transfer within the same AWS Region between Fargate tasks and other AWS services or for data transfer between Fargate tasks within the same Availability Zone. However, standard AWS data transfer charges apply for data transfer between Fargate tasks and external services or between Fargate tasks in different Availability Zones.
-
Elastic Load Balancer (ELB): If you use an Elastic Load Balancer (ELB) to distribute traffic to your Fargate tasks, you are charged for the use of the ELB separately based on its pricing model (e.g., per hour or per GB of data processed).
-
Data Storage: Fargate does not charge for data storage directly, but if your containers use services such as Amazon EBS (Elastic Block Store) volumes or Amazon S3 for data storage, you are billed for the usage of those services according to their pricing models.
-
CloudWatch Logs: Fargate automatically sends container logs to Amazon CloudWatch Logs. You are charged for the storage of logs in CloudWatch Logs and for any additional features such as log metric filters or log-based alarms.
-
Spot Pricing: AWS Fargate offers the option to use Spot Instances, which allows you to take advantage of spare capacity in the AWS cloud at reduced prices. Spot Instances can help you save costs compared to On-Demand Instances, but they are subject to availability and may be interrupted with short notice.
It's important to carefully consider these pricing factors when planning and provisioning resources for your containerized applications running on AWS Fargate. You can use the AWS Pricing Calculator to estimate the cost of running your Fargate tasks based on your specific resource requirements and usage patterns.
