## AWS Lambda Pricing

The price for Duration depends on the amount of memory you allocate to your function. You can allocate any amount of memory to your function between 128MB and 3008MB, in 64MB increments. The table below contains a few examples of the price per 100ms associated with different memory sizes.

All examples below are based on price in US East (N. Virginia).

• ### Example 1

If you allocated 512MB of memory to your function, executed it 3 million times in one month, and it ran for 1 second each time, your charges would be calculated as follows:
If you allocated 512MB of memory to your function, executed it 3 million times in one month, and it ran for 1 second each time, your charges would be calculated as follows:

Monthly compute charges

The monthly compute price is \$0.00001667 per GB-s and the free tier provides 400,000 GB-s.

Total compute (seconds) = 3M * (1s) = 3,000,000 seconds

Total compute (GB-s) = 3,000,000 * 512MB/1024 = 1,500,000 GB-s

Total compute – Free tier compute = Monthly billable compute GB- s

1,500,000 GB-s – 400,000 free tier GB-s = 1,100,000 GB-s

Monthly compute charges = 1,100,000 * \$0.00001667 = \$18.34

Monthly request charges

The monthly request price is \$0.20 per 1 million requests and the free tier provides 1M requests per month.

Total requests – Free tier requests = Monthly billable requests

3M requests – 1M free tier requests = 2M Monthly billable requests

Monthly request charges = 2M * \$0.2/M = \$0.40

Total monthly charges

Total charges = Compute charges + Request charges = \$18.34 + \$0.40 = \$18.74 per month

• ### Example 2

If you allocated 128MB of memory to your function, executed it 30 million times in one month, and it ran for 200ms each time, your charges would be calculated as follows:
If you allocated 128MB of memory to your function, executed it 30 million times in one month, and it ran for 200ms each time, your charges would be calculated as follows:

Monthly compute charges

The monthly compute price is \$0.00001667 per GB-s and the free tier provides 400,000 GB-s.

Total compute (seconds) = 30M * (0.2sec) = 6,000,000 seconds

Total compute (GB-s) = 6,000,000 * 128MB/1024 = 750,000 GB-s

Total Compute – Free tier compute = Monthly billable compute seconds

750,000 GB-s – 400,000 free tier GB-s = 350,000 GB-s

Monthly compute charges = 350,000 * \$0.00001667 = \$5.83

Monthly request charges

The monthly request price is \$0.20 per 1 million requests and the free tier provides 1M requests per month.

Total requests – Free tier request = Monthly billable requests

30M requests – 1M free tier requests = 29M Monthly billable requests

Monthly request charges = 29M * \$0.2/M = \$5.80

Total compute charges

Total charges = Compute charges + Request charges = \$5.83 + \$5.80 = \$11.63 per month

• ### Example 3

This example shows how charges are calculated when you are running functions with different memory sizes. For the example, let’s assume you have three functions, each with different memory sizes as described below:
This example shows how charges are calculated when you are running functions with different memory sizes. For the example, let’s assume you have three functions, each with different memory sizes as described below:

Function 1

128MB of memory, executed 25M times in one month, runs for 200ms each time

Total compute (seconds) = 25M * (0.2sec) = 5M seconds

Function 2

448MB of memory, executed 5M times in one month, runs for 500ms each time

Total compute (seconds) = 5M * (0.5sec) = 2M seconds

Function 3

1024MB of memory, executed 2.5M times in one month, runs for 1 second each time

Total compute (seconds) = 2.5M * (1sec) = 2.5M seconds

If you ran these functions, your charges would be calculated as follows:

Monthly compute charges

AWS Lambda normalizes the total compute time to GB-s and then sums the total across all functions

Function 1 (GB-S) = 5M seconds * (128MB/1024) = 625,000 GB-s

Function 2 (GB-S) = 2.5M seconds * (448MB/1024) = 1,093,750 GB-s

Function 3 (GB-S) = 2.5M seconds * (1024MB/1024) = 2,500,000 GB-s

Total monthly compute usage (GB-S) = 4,218,750 GB-s

The monthly compute price is \$0.00001667 per GB-s and the free tier provides 400,000 GB-s.

Monthly charged compute usage = Total monthly compute usage – Free tier usage

Monthly charged compute usage = 4,218,750 – 400,000 = 3,818,750 GB-s

Monthly compute charges = 3,818,750 * 0.00001667 = \$63.66

Monthly request charges

The monthly request price is \$0.20 per 1 million requests and the free tier provides 1M requests per month.

Total requests – Free tier requests = Monthly billable requests

(25M+5M+2.5M) requests – 1M free tier requests = 31.5M Monthly billable requests

Monthly request charges = 31.5M * \$0.2/M = \$6.30

Total Monthly Charges

Total charges = Compute charges + Request charges = \$63.66 + \$6.30 = \$69.96 per month

* Duration charges apply to code that runs in the handler of a function as well as initialization code that is declared outside of the handler. For more details, see the Lambda Programming Model documentation

## Provisioned Concurrency Pricing

You can enable Provisioned Concurrency for your Lambda functions for greater control over the performance of your serverless applications. When enabled, Provisioned Concurrency keeps functions initialized and hyper-ready to respond in double-digit milliseconds. You pay for the amount of concurrency that you configure and for the period of time that you configure it. When Provisioned Concurrency is enabled for your function and you execute it, you also pay for Requests and Duration based on the prices below. If the concurrency for your function exceeds the configured concurrency, you will be billed for executing the excess functions at the rate outlined in the AWS Lambda Pricing section above. To learn more about Provisioned Concurrency, visit the documentation.

Provisioned Concurrency is calculated from the time you enable it on your function until it is disabled, rounded up to the nearest 5 minutes. The price depends on the amount of memory you allocate to your function and the amount of concurrency that you configure on it.

Duration is calculated from the time your code begins executing until it returns or otherwise terminates, rounded up to the nearest 100ms**. The price depends on the amount of memory you allocate to your function.

The Lambda free tier does not apply to functions that have Provisioned Concurrency enabled. If you enable Provisioned Concurrency for your function and execute it, you will be charged for Requests and Duration based on the price below.

All examples below are based on price in US East (N. Virginia).

** Duration charges apply to code that runs in the handler of a function as well as initialization code that is declared outside of the handler. For functions configured with Provisioned Concurrency, AWS Lambda periodically recycles the execution environments and re-runs your initialization code. For more details, see the Lambda Programming Model documentation

## Data Transfer & Other Charges

Data Transfer
Data transferred “in” to and “out” of your AWS Lambda functions from outside the region the function executed in will be charged at the EC2 data transfer rates as listed here under “Data transfer”.

Data transferred between Amazon S3, Amazon Glacier, Amazon DynamoDB, Amazon SES, Amazon SQS, Amazon Kinesis, Amazon ECR, Amazon SNS, Amazon EFS, or Amazon SimpleDB and AWS Lambda functions in the same AWS Region is free. The usage of VPC or VPC peering with AWS Lambda functions will incur additional charges as explained here.

You may incur additional charges if your Lambda function utilizes other AWS services or transfers data. For example, if your Lambda function reads and writes data to or from Amazon S3, you will be billed for the read/write requests and the data stored in Amazon S3.

For details on AWS service pricing, see the pricing section of the relevant AWS service detail pages.

## Lambda@Edge Pricing

Lambda@Edge functions are metered at a granularity of 50ms