AWS Lambda
Read the Lambda functions in an account, with their execution roles, aliases, event source mappings and function policies.
Read function configuration
Kian’s AWS account inventory lists the Lambda functions in the selected regions with their aliases, event source mappings and function policies. A function record keeps its runtime, handler, execution role, VPC settings, timeout, memory, layers, log group and code hash.
Environment variable values are skipped as Lambda’s response is parsed, so only the names are stored. Kian never requests function code or its download location.
Compare a change with the deployed function
Suppose a change adds an environment variable that a handler reads, or moves a function to a new execution role. The recorded variable names and role give the reviewer the function’s configuration to compare with that change.
When an alarm on a function’s metric starts an investigation, it cites the function’s record and counts events in the log groups its configurations name. Kian evaluates no invocation, function policy or execution-role permission from these records.
Connect your AWS account
Choose the AWS account and region for the environment under review. Apply the read role from the CloudFormation or Terraform files with the account inventory grant selected and every region your environments read. Without the grant, these reads stay named collection gaps.
Turn on the production loop for AWS
Get started with GitHub