Term
Definition
AWS Lambda
Serverless compute service that runs your code in response to triggers without managing servers - you just upload code and it executes
Serverless Computing
Running code without provisioning or managing servers - AWS handles all the infrastructure so you focus on code
Lambda Function
The actual code package you upload to Lambda that executes when triggered - contains your business logic
Triggers
Events that cause Lambda functions to execute - can be HTTP requests or AWS service events
Code (Lambda context)
Your actual business logic written in supported languages like Python or Node.js that gets executed
Underlying Compute Resources
The servers and infrastructure AWS manages for you - you never see or configure these directly
Run Your Code
Lambda executes your function when triggered - handles all the compute automatically
Scale Your Code
Lambda automatically adds or removes compute capacity based on incoming requests - no manual scaling needed
High Availability
Lambda runs across multiple availability zones automatically - built-in redundancy without configuration
Lambda Code Editor
Web-based IDE in AWS console for writing and editing Lambda functions directly
HTTP Endpoints
API Gateway URLs that trigger Lambda functions for web services - creates REST APIs
In-app Activity
Events within applications that can trigger Lambda functions - like mobile app actions
Scheduled Triggers
CloudWatch Events/EventBridge rules that run Lambda on a schedule - like cron jobs
No Servers to Manage
You never provision EC2 instances or manage operating systems - AWS handles everything
Continuous Scaling
Lambda automatically scales from zero to thousands of concurrent executions instantly
Trigger-1 Trigger-2 Process
Lambda can respond to multiple trigger types and process them with the same or different functions
Subsecond Metering
You’re billed in 1ms increments only for actual compute time used - not idle time
Pay Only for What You Use
No charges when code isn’t running - only pay for requests and compute duration
Pricing Based on Requests
Charged per million requests to invoke your functions
Duration-based Pricing
Charged for compute time in GB-seconds - memory allocated times execution duration
Time Increments of 1ms
Billing calculated down to the millisecond for precise cost optimization
Code Not Running = $0.00
Zero charges when Lambda functions are idle - no minimum fees or idle costs
AWS Lambda Triggers (Examples)
Various AWS services that can invoke Lambda functions through events