Functions · 3 November 2026

AWS Lambda API

Functions now accept the AWS Lambda API, signed with AWS Signature Version 4, so code that uses AWS's SDKs (such as boto3) runs against Runtime Functions after you change only the endpoint and the keys. Create an access key pair with POST /v2/aws-access-keys, authenticated with a Runtime API key; it returns accessKeyId and secretAccessKey, reaches what that API key reaches, and stops working when that API key is revoked or expires. Set AWS_ENDPOINT_URL_LAMBDA to https://<your API host>, set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY to the pair, and use a function's ID as FunctionName. GetFunction (FunctionName, MemorySize, Environment and LastModified), ListFunctions with Marker and MaxItems, and DeleteFunction are supported. Errors return Lambda's exception names, such as ResourceNotFoundException. A qualified function name or an ARN returns 400 InvalidParameterValueException. Invoke, CreateFunction, UpdateFunctionCode, UpdateFunctionConfiguration, versions and aliases are not yet available and return 404.