The first, the most popular, and arguably the most feature-rich event-driven, serverless computing platform.
AWS Lambda runs functions based on triggers and bills based on time and data transfer.
Lambda offers a number of capabilities that integrate and run across these building blocks. These include Lambda Applications, a combination of Lambda functions, event sources, and other resources that work together to perform tasks, AWS Serverless Application Repository, and AWS CloudFormation.
A wide variety of sources can trigger Lambda functions. Sources can be grouped into AWS-native and non-native. The native bucket includes sources like Kinesis, Cognito, SNS and Simple Email Service.
Non-AWS event sources can trigger functions in two ways: via the AWS API Gateway, and via EventBridge. EventBridge is a serverless event bus that connects application data from your own apps, SaaS, and AWS services.
You create Lambda triggers differently depending on the type of event source. For AWS-native Read Events, you create an event source mapping and grant Lambda permission to access the other service in the execution role. With synchronous invocation, you grant the service permission in the function’s resource-based policy, and configure the service to generate events and invoke function. For asynchronous, Lambda queues the event before passing it to your function.
Events sourced from the API Gateway use proxy or non-proxy integration.
EventBridge provides a console for setting up trigger rules.
Services send event data to functions in JSON. The structure of the event document is different for each event type, and contains data about the resource or request that triggered the function.
Lambda supports a wide number of languages: Node.js, Python, Ruby, Java, Go, .Net Core, or you can implement a custom runtime to use other languages.
Use the Lambda console to configure function settings, add triggers and destinations, and update and test your code.
With the console, you can configure: triggers, layers (custom runtimes, dependencies, etc.), destinations, and a number of settings, such as code, runtime, tags, roles, memory, description, timeout and more.
The only way to run a function in AWS is to deploy it to the Lambda service.
Find answers to common questions or reach out to our support