Audit a Function's Versions, Aliases, and Event Sources
A 5-step recipe with AWS Lambda. We can help you get access.
Recipe · 5 steps
Audit a Function's Versions, Aliases, and Event Sources
with AWS Lambda · IT Infrastructure Management
Inventory a function's configuration, versions, aliases, and event source mappings.
- List the functions in the region to establish the account-level inventory the audited function sits in. FunctionVersion is left unset so the response carries the unpublished $LATEST configuration of each function rather than an entry per pu
- Read the live configuration of the audited function — runtime, role, memory, timeout, layers, and state. This is the $LATEST configuration, which is what the next published version will snapshot.
- List the published versions. Each is an immutable snapshot of code and configuration, so this is the deployment history an auditor can roll back to.
- List the aliases and the versions they point at. This is what reveals which version is actually serving production traffic, and whether any alias is mid-canary with a weighted routing config.
- List the event sources invoking this function, completing the picture of what can trigger it. LastProcessingResult on each mapping is the fastest signal that a source is failing.
What you'll need to have ready
- functionName: The name or ARN of the function to audit in depth.
- maxItems: Maximum number of items returned per list call (1-10000).
For your developer
Arazzo workflow aws-lambda:function-inventory-audit, 5 operations: ListFunctions → GetFunctionConfiguration → ListVersionsByFunction → ListAliases → ListEventSourceMappings. Specs on APIs.io.