AWS Lambda

2020/01/20 - 8 updated api methods

Changes   Added reason codes to StateReasonCode (InvalidSubnet, InvalidSecurityGroup) and LastUpdateStatusReasonCode (SubnetOutOfIPAddresses, InvalidSubnet, InvalidSecurityGroup) for functions that connect to a VPC.

2019/12/04 - 5 new api methods

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.

2019/11/25 - 5 new 13 updated api methods

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.

2019/11/19 - 13 updated api methods

Changes   This release provides three new runtimes to support Node.js 12 (initially 12.13.0), Python 3.8 and Java 11.

2019/08/29 - 5 updated api methods

Changes   Adds a "MaximumBatchingWindowInSeconds" parameter to event source mapping api's. Usable by Dynamodb and Kinesis event sources.

2019/05/13 - 13 updated api methods

Changes   AWS Lambda now supports Node.js v10

2019/04/25 - 1 new api methods

Changes   AWS Lambda now supports the GetLayerVersionByArn API.

2018/11/29 - 8 new 8 updated api methods

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.

2018/11/20 - 8 updated api methods

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.

2018/07/09 - 8 updated api methods

Changes   Add support for .NET Core 2.1 to Lambda.

2018/04/03 - 8 updated api methods

Changes   added nodejs8.10 as a valid runtime

2018/01/25 - 15 updated api methods

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.

2018/01/15 - 8 updated api methods

Changes   Support for creating Lambda Functions using 'dotnetcore2.0' and 'go1.x'.

2017/11/30 - 2 new 2 updated api methods

Changes   AWS Lambda now supports the ability to set the concurrency limits for individual functions, and increasing memory to 3008 GB.

2017/11/29 - 5 updated api methods

Changes   Lambda aliases can now shift traffic between two function versions, based on preassigned weights.

2017/07/17 - 8 updated api methods

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.

2017/05/04 - 1 updated api methods

Changes   Support for UpdateFunctionCode DryRun option

2017/04/19 - 8 updated api methods

Changes   Lambda integration with CloudDebugger service to enable customers to enable tracing for the Lambda functions and send trace information to the CloudDebugger service.

2017/04/18 - 3 new 8 updated api methods

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.

2017/03/22 - 8 updated api methods

Changes   Adds support for new runtime Node.js v6.10 for AWS Lambda service. :tada:

2016/12/01 - 1 new 9 updated api methods

Changes   Adds new API `getAccountSettings`, dotnetcore 1.0 runtime support, DeadLetterConfig, and event source mappings with kinesis streams.

2016/11/18 - 8 updated api methods

Changes   Adds support for Environment variables.