What is AWS Lambda?
AWS Lambda executes application code in response to events without requiring a team to manage the underlying servers. This profile focuses on Lambda Event Functions; other execution offers, concurrency options and connected AWS services need separate checks.
Who is AWS Lambda for?
Teams defining event-processing or backend tasks within an AWS application architecture.
Define the event and the completed task
AWS Lambda lets developers run application code without managing the underlying servers. For this profile, the cost and runtime discussion focuses on Event Functions. A broader AWS architecture can include other execution products and separately metered services.
Start with one event and an observable result: what input arrives, what record changes, what response is returned and what happens when delivery is repeated. Compare Azure Functions or Workers around the same task. For an application packaged around containers or jobs, also review Cloud Run as a different execution arrangement.
AWS Lambda features
The core capabilities to consider for your workflow.
- Event-triggered application functions
- Managed execution environments
- Memory- and duration-based compute metering
AWS Lambda pricing
Usage-based; conditional free allowance
Estimate requests and memory-duration compute, then add any relevant concurrency, storage, event delivery, logging and other connected services. Use the actual architecture and region rather than a single request count as the total application bill.
Calculate the cost of your quote →Free access & evaluation
The reviewed Event Functions pricing includes a monthly free allowance of one million requests and 400,000 GB-seconds. Eligibility, account terms, configuration and other AWS service usage still matter.
Before you choose AWS Lambda
A Lambda allowance is not a guarantee that the whole connected application is free.
Provisioned Concurrency does not receive the reviewed Lambda free tier.
Event Function runtime limits are distinct from other Lambda execution offers.
Budget memory-duration usage as well as request count
The Lambda pricing page separates requests from compute measured in GB-seconds. More allocated memory changes the compute measure for a given duration. Include relevant connected services rather than treating a request allowance as the complete application budget.
Match the task to the Event Function timeout. Choose a realistic timeout and define the expected behaviour if work exceeds it. Separately consider whether the application needs Provisioned Concurrency; the reviewed free tier does not apply when it is enabled. Record configuration, region, expected events and operating requirements before comparing a total estimate.
Explore related software
AWS Lambda FAQs
Does AWS Lambda include 1 million free requests every month?
The reviewed pricing lists one million requests and 400,000 GB-seconds per month. Account eligibility, configuration and connected service costs still need checking.
What is the maximum timeout for Lambda Event Functions?
The documented default is 3 seconds, configurable in one-second increments up to 900 seconds, or 15 minutes. This answer concerns Event Functions.
Does the Lambda free tier cover Provisioned Concurrency?
No. The reviewed pricing says the free tier does not apply to functions with Provisioned Concurrency enabled. Its request and duration billing must be assessed separately.
Does staying inside the Lambda free allowance make my whole AWS application free?
No. Other services and configurations can create charges. Estimate the full architecture rather than only the Event Function request allowance.
Why does Lambda memory allocation affect compute usage?
Compute is measured using allocated memory and execution duration in GB-seconds. Request count alone does not describe the amount of compute used.