Changes Adds support for logging configuration in Lambda Functions. Customers will have more control how their function logs are captured and to which cloud watch log group they are delivered also.
Changes Add Java 21 (java21) support to AWS Lambda
Changes Add Python 3.12 (python3.12) support to AWS Lambda
Changes Add Custom runtime on Amazon Linux 2023 (provided.al2023) support to AWS Lambda.
Changes Add Node 20 (nodejs20.x) support to AWS Lambda.
Changes Adds support for Lambda functions to access Dual-Stack subnets over IPv6, via an opt-in flag in CreateFunction and UpdateFunctionConfiguration APIs
Changes Add Python 3.11 (python3.11) support to AWS Lambda
Changes Add Ruby 3.2 (ruby3.2) Runtime support to AWS Lambda.
Changes Add Java 17 (java17) support to AWS Lambda
Changes Add Python 3.10 (python3.10) support to AWS Lambda
Changes This release adds a new Lambda InvokeWithResponseStream API to support streaming Lambda function responses. The release also adds a new InvokeMode parameter to Function Url APIs to control whether the response will be streamed or buffered.
Changes This release adds the ability to create ESMs with Document DB change streams as event source. For more information see https://docs.aws.amazon.com/lambda/latest/dg/with-documentdb.html.
Changes Release Lambda RuntimeManagementConfig, enabling customers to better manage runtime updates to their Lambda functions. This release adds two new APIs, GetRuntimeManagementConfig and PutRuntimeManagementConfig, as well as support on existing Create/Get/Update function APIs.
Changes Add support for MaximumConcurrency parameter for SQS event source. Customers can now limit the maximum concurrent invocations for their SQS Event Source Mapping.
Changes Adds support for Lambda SnapStart, which helps improve the startup performance of functions. Customers can now manage SnapStart based functions via CreateFunction and UpdateFunctionConfiguration APIs
Changes Add Node 18 (nodejs18.x) support to AWS Lambda.
Changes Added support for customization of Consumer Group ID for MSK and Kafka Event Source Mappings.
Changes Lambda releases NodeJs 16 managed runtime to be available in all commercial regions.
Changes This release adds new APIs for creating and managing Lambda Function URLs and adds a new FunctionUrlAuthType parameter to the AddPermission API. Customers can use Function URLs to create built-in HTTPS endpoints on their functions.
Changes Adds support for increased ephemeral storage (/tmp) up to 10GB for Lambda functions. Customers can now provision up to 10 GB of ephemeral storage per function instance, a 20x increase over the previous limit of 512 MB.
Changes Adds PrincipalOrgID support to AddPermission API. Customers can use it to manage permissions to lambda functions at AWS Organizations level.
Changes Lambda releases .NET 6 managed runtime to be available in all commercial regions.
Changes Release Lambda event source filtering for SQS, Kinesis Streams, and DynamoDB Streams.
Changes Add support for Lambda Function URLs. Customers can use Function URLs to create built-in HTTPS endpoints on their functions.
Changes Added support for CLIENT_CERTIFICATE_TLS_AUTH and SERVER_ROOT_CA_CERTIFICATE as SourceAccessType for MSK and Kafka event source mappings.
Changes Adds support for Lambda functions powered by AWS Graviton2 processors. Customers can now select the CPU architecture for their functions.
Changes Lambda Python 3.9 runtime launch
Changes Added support for AmazonMQRabbitMQ as an event source. Added support for VIRTUAL_HOST as SourceAccessType for streams event source mappings.
Changes Support for creating Lambda Functions using 'nodejs14.x'
Changes Added support for Apache Kafka as a event source. Added support for TumblingWindowInSeconds for streams event source mappings. Added support for FunctionResponseTypes for streams event source mappings
Changes Added the additional enum InvalidImage to StateReasonCode and LastUpdateStatusReasonCode fields.
Changes This release includes support for a new feature: Container images support in AWS Lambda. This adds APIs for deploying functions as container images. AWS Lambda now supports memory up to 10240MB.
Changes This release includes support for new feature: Code Signing for AWS Lambda. This adds new resources and APIs to configure Lambda functions to accept and verify signed code artifacts at deployment.
Changes Added the starting position and starting position timestamp to ESM Configuration. Now customers will be able to view these fields for their ESM.
Changes Support Amazon MQ as an Event Source.
Changes Support for creating Lambda Functions using 'java8.al2' and 'provided.al2'
Changes Support Managed Streaming for Kafka as an Event Source. Support retry until record expiration for Kinesis and Dynamodb streams event source mappings.
Changes Adds support for using Amazon Elastic File System (persistent storage) with AWS Lambda. This enables customers to share data across function invocations, read large reference data files, and write function output to a persistent and shared store.
Changes AWS Lambda now supports .NET Core 3.1
Changes AWS Lambda now supports Ruby 2.7
Changes Added reason codes to StateReasonCode (InvalidSubnet, InvalidSecurityGroup) and LastUpdateStatusReasonCode (SubnetOutOfIPAddresses, InvalidSubnet, InvalidSecurityGroup) for functions that connect to a VPC.
Changes - Added the ProvisionedConcurrency type and operations. Allocate provisioned concurrency to enable your function to scale up without fluctuations in latency. Use PutProvisionedConcurrencyConfig to configure provisioned concurrency on a version of a function, or on an alias.
Changes Added the function state and update status to the output of GetFunctionConfiguration and other actions. Check the state information to ensure that a function is ready before you perform operations on it. Functions take time to become ready when you connect them to a VPC.Added the EventInvokeConfig type and operations to configure error handling options for asynchronous invocation. Use PutFunctionEventInvokeConfig to configure the number of retries and the maximum age of events when you invoke the function asynchronously.Added on-failure and on-success destination settings for asynchronous invocation. Configure destinations to send an invocation record to an SNS topic, an SQS queue, an EventBridge event bus, or a Lambda function.Added error handling options to event source mappings. This enables you to configure the number of retries, configure the maximum age of records, or retry with smaller batches when an error occurs when a function processes a Kinesis or DynamoDB stream.Added the on-failure destination setting to event source mappings. This enables you to send discarded events to an SNS topic or SQS queue when all retries fail or when the maximum record age is exceeded when a function processes a Kinesis or DynamoDB stream.Added the ParallelizationFactor option to event source mappings to increase concurrency per shard when a function processes a Kinesis or DynamoDB stream.
Changes This release provides three new runtimes to support Node.js 12 (initially 12.13.0), Python 3.8 and Java 11.
Changes Adds a "MaximumBatchingWindowInSeconds" parameter to event source mapping api's. Usable by Dynamodb and Kinesis event sources.
Changes AWS Lambda now supports Node.js v10
Changes AWS Lambda now supports the GetLayerVersionByArn API.
Changes AWS Lambda now supports Lambda Layers and Ruby as a runtime. Lambda Layers are a new type of artifact that contains arbitrary code and data, and may be referenced by zero, one, or more functions at the same time. You can also now develop your AWS Lambda function code using the Ruby programming language.
Changes AWS Lambda now supports python3.7 and the Kinesis Data Streams (KDS) enhanced fan-out and HTTP/2 data retrieval features for Kinesis event sources.
Changes Add support for .NET Core 2.1 to Lambda.
Changes added nodejs8.10 as a valid runtime
Changes AWS Lambda now supports Revision ID on your function versions and aliases, to track and apply conditional updates when you are updating your function version or alias resources.
Changes Support for creating Lambda Functions using 'dotnetcore2.0' and 'go1.x'.
Changes AWS Lambda now supports the ability to set the concurrency limits for individual functions, and increasing memory to 3008 GB.
Changes Lambda aliases can now shift traffic between two function versions, based on preassigned weights.
Changes Lambda@Edge lets you run code closer to your end users without provisioning or managing servers. With Lambda@Edge, your code runs in AWS edge locations, allowing you to respond to your end users at the lowest latency. Your code is triggered by Amazon CloudFront events, such as requests to and from origin servers and viewers, and it is ready to execute at every AWS edge location whenever a request for content is received. You just upload your Node.js code to AWS Lambda and Lambda takes care of everything required to run and scale your code with high availability. You only pay for the compute time you consume - there is no charge when your code is not running.
Changes Support for UpdateFunctionCode DryRun option
Changes Lambda integration with CloudDebugger service to enable customers to enable tracing for the Lambda functions and send trace information to the CloudDebugger service.
Changes You can use tags to group and filter your Lambda functions, making it easier to analyze them for billing allocation purposes. For more information, see Tagging Lambda Functions. You can now write or upgrade your Lambda functions using Python version 3.6. For more information, see Programming Model for Authoring Lambda Functions in Python. Note: Features will be rolled out in the US regions on 4/19.
Changes Adds support for new runtime Node.js v6.10 for AWS Lambda service. :tada:
Changes Adds new API `getAccountSettings`, dotnetcore 1.0 runtime support, DeadLetterConfig, and event source mappings with kinesis streams.
Changes Adds support for Environment variables.