Lambda functions in a region

Lists every Lambda function in a region with the configuration that answers most inventory asks - runtime, architecture, memory, timeout and execution role - in a single call. Lambda is regional, so fan out over the enabled regions from aws/ec2/regions-enabled for an account-wide inventory.

Query

SELECT
function_name,
runtime,
json_extract(architectures, '$[0]') as architecture,
memory_size,
timeout,
package_type,
code_size,
last_modified,
role
FROM aws.lambda.functions
WHERE region = '{{region}}';

Variation: cheap name-only enumeration

The Cloud Control list-only resource returns identifiers alone, which is enough when the next step is a keyed read per function:

SELECT function_name
FROM awscc.lambda.functions_list_only
WHERE region = '{{region}}';

Variation: full detail for one function

Supplying function_name routes to GetFunction, which returns the code location, concurrency and tags alongside the configuration - none of which appear in the list response:

SELECT code, configuration, concurrency, tags
FROM aws.lambda.functions
WHERE region = '{{region}}'
AND function_name = 'my-function';

Notes

The same resource serves two operations: region alone lists every function with full configuration, while adding function_name routes to GetFunction and returns a different column set (code, configuration, concurrency, tags), so a projection valid for one form fails against the other. architectures is a JSON array - functions declare exactly one architecture today, so element 0 is the value. runtime is null for container image functions, where package_type is Image and the runtime lives in the image itself. memory_size determines CPU allocation as well as memory. The awscc list-only variation needs cloudformation:ListResources in addition to the Lambda action.