AWS Lambda Pricing Model Explained With Examples

Money is the one thing that turns the world around. Unfortunately, it is the necessity in almost all spheres of life. You can live without it or with lesser amounts of it, but it makes it all harder. If you wish to have it, first, you need to give it, as always. Even AWS Lambda is not free.

Simply put, you have an idea and are on a breakthrough to make it happen. You need to use AWS Lambda to make it easier, prettier or for whatever reason, easier to maintain. You need to pay for AWS Lambda. In that way, your product will see the light of the day which will eventually bring the money back to you. To be able to earn, you need to invest first.

A good thing with AWS Lambda prices is that you will only pay for what you use. There are no pre-set packages of their service where you will end up paying for something that you might not use at all. That’s why AWS Lambda decided to make it as simple as possible, which is a fantastic feature.

How Does AWS Lambda Charge For Their Services?

AWS Lambda is charging its users by the number of requests for their functions and by the duration, which is the time the code needs to execute. When code starts running in response to an event, AWS Lambda counts a request. It will charge the total number of requests across all of the functions used. Duration is calculated by the time when your code started executing until it returns or until it is terminated, rounded up near to 100ms. The AWS Lambda pricing depends on the amount of memory that the user used to allocate to the function.

AWS Lambda Pricing Model Explained

The Free Tier includes 1 million requests per month, and 400,000 GB-seconds of compute time on a monthly basis. The Lambda Free Tier doesn’t expire automatically at the end of the annual AWS Free Tier term. It is available indefinitely to both existing and new AWS customers.

In the upcoming example, we’ll show you some of the approximate prices per 100ms associated with different memory sizes in the free tier seconds. The lowest example would be to allocate 128 MB of memory within the limit of 3.2 million seconds per month. The price per 100ms would be $US 0.000000208.

Another example will lead us somewhere around the middle price. Let’s say that you allocate 1600 MB of memory inside the 256,000 seconds per month limit in the free tier. Choosing these parameters would cost you $US 0.000002605 per 100ms.

A third example would probably be the highest in cost but let us show it to you. Considering that you choose to allocate 3008 MB of memory with the limit of 136,170 seconds per month in the free tier. You’d need to pay for this $US 0.000004897 per 100ms. There are many more choices to choose from with more or less allocated memory, leading to more or less free tier seconds, and finally, a different price per 100ms used.

The Requests Tier includes 1 million free requests per month. After they’ve been spent, this tier will cost $0.20 per 1 million requests or $0.0000002 per a single request.

The Duration Tier comes free with 400,000 GB-seconds per month, which is up to 3.2 million seconds of computing time that are free of charge. After they’ve been spent, this tier costs will go to $0.00001667 per every GB-second used. The price is based upon the amount of memory allocated to the user’s function.

If this information was helpful, but it still gives you a hard time to calculate the price you’d need to pay, use our AWS Lambda cost calculator. The calculator might help you in figuring out the costs you need to pay for AWS Lambda services based on personal usage. Follow this link and calculate your own AWS Lambda prices.

Additional Charges Within AWS Lambda Pricing

People mostly do not like the “small text on the bottom,” and usually they do not read it through. That is why we at Dashbird have read it all, and we wish to deliver it to you. That way you will avoid any unnecessary and unpleasant experiences.

To avoid unnecessary situations, you need to know everything there is to know about pricing models, additional charges, etc. Are there any additional charges in AWS Lambda pricing models? Yes, there are. Read this carefully, and there will be no unpleasant surprises.

The possibility of additional costs to incur is significantly higher if you have used any other AWS services or data transfers. You will be charged regardless of the chosen tier. In the example, if your function is reading and writing data to or from Amazon S3, you will be charged for the read/write requests and all of the data that is stored within Amazon S3.

We will list some of the cases that will be charged additionally and that way you can follow up with all the changes made. If your Lambda function starts the external data transfers, you will be billed at the EC2 data transfer rate.

Also, something worth mentioning is that Amazon DynamoDB charges for data storage, as well as for throughput capacity and data transfer. On the other hand, Amazon S3 is charging for storage, requests and data transfers.

AWS Lambda Pricing Examples

The AWS Lambda pricing example will be presented in this section made by the AWS Lambda prices already mentioned.

Let say, if you allocated 512 MB of memory to your function and executed it 3 million times during one months time. Considering that it ran for 1 second each time, you’d be billed upon monthly compute time (in this case = $18.34) and by monthly requests (in this case = $0.40). Therefore, the total billed sum would be $18.74 per month.

That being said, AWS Lambda is amazing for cutting costs and we’ve had plenty of examples where companies have managed to save up big by switching to Serverless. Coca-Cola North America has seen a lot of benefit from going serverless on their vending machines division so much so that they’ve made serverless a requirement for their development division.

Knowing what you need and how much it might cost are the first steps to fulfilling your ideas and bring them to life.

Let us know if there is something you wish to discuss this topic or if you have an opinion you want to share. Be free to leave a comment in the section below.

We aim to improve Dashbird every day and user feedback is extremely important for that, so please let us know if you have any feedback about these improvements and new features! We would really appreciate it!

Read our blog

Top 6 AWS Lambda Monitoring Tools

Monitoring helps you identify any performance issues, and it can also send you alerts and notify you of anything you might need to know. This article will cover the top 6 AWS Lambda monitoring tools and explain how they work and are used.

8 Common Mistakes When Using AWS ECS to Manage Containers

In this article, we’ll discuss the potential pitfalls that we came across when configuring ECS task definitions. While considering this AWS-specific container management platform, we’ll also examine some general best practices for working with containers in production.

AWS Lambda Cost Optimization Strategies That Work

From caching Lambda responses to building smaller functions to choosing the right memory configs. In this article, we’re exploring six specific steps you can take to optimize your AWS Lambda costs.

More articles

Made by developers for developers

Dashbird was born out of our own need for an enhanced serverless debugging and monitoring tool, and we take pride in being developers.

What our customers say

Dashbird gives us a simple and easy to use tool to have peace of mind and know that all of our Serverless functions are running correctly. We are instantly aware now if there’s a problem. We love the fact that we have enough information in the Slack notification itself to take appropriate action immediately and know exactly where the issue occurred.

Thanks to Dashbird the time to discover the occurrence of an issue reduced from 2-4 hours to a matter of seconds or minutes. It also means that hundreds of dollars are saved every month.

Great onboarding: it takes just a couple of minutes to connect an AWS account to an organization in Dashbird. The UI is clean and gives a good overview of what is happening with the Lambdas and API Gateways in the account.

I mean, it is just extremely time-saving. It’s so efficient! I don’t think it’s an exaggeration or dramatic to say that Dashbird has been a lifesaver for us.

Dashbird provides an easier interface to monitor and debug problems with our Lambdas. Relevant logs are simple to find and view. Dashbird’s support has been good, and they take product suggestions with grace.

Great UI. Easy to navigate through CloudWatch logs. Simple setup.

Dashbird helped us refine the size of our Lambdas, resulting in significantly reduced costs. We have Dashbird alert us in seconds via email when any of our functions behaves abnormally. Their app immediately makes the cause and severity of errors obvious.