IAM policy example: invoke one Lambda function, with a least privilege rewrite
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Allows a principal to invoke a single Lambda function, my-function, in one Region and account. The original uses lambda:* on every function. The rewrite keeps one action and one function ARN. Resource names and account 111122223333 are placeholders used in AWS documentation.
Open the workbench ยท All examples
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "InvokeAny",
"Effect": "Allow",
"Action": "lambda:*",
"Resource": "*"
}
]
}
What it allows
- Allows every Lambda action on every function in every Region.
What it allows
Allow 135 actions (lambda:*) on every resource.
Action or pattern Actions Access levels lambda:*135 List 25, Read 32, Write 68, Permissions management 8, Tagging 2
Checks
- High Allows 76 write or permissions-management actions (8 permissions management) on every resource ("Resource": "*"). AWS documentation for this check
The action lambda:* covers 135 actions, including code updates and permission changes on all functions.
Least privilege rewrite
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "InvokeOne",
"Effect": "Allow",
"Action": "lambda:InvokeFunction",
"Resource": "arn:aws:lambda:us-east-1:111122223333:function:my-function"
}
]
}
The rewrite grants InvokeFunction on one function ARN. Updating code and editing function permissions are removed.
What it allows
Allow 1 action (lambda:InvokeFunction) on arn:aws:lambda:us-east-1:111122223333:function:my-function.
Action or pattern Actions Access levels lambda:InvokeFunction1 Write 1
Checks
No flags from the six checks.
Related pages
Sources
- AWS Lambda Developer Guide: permissions, read 16 Nov 2026
- AWS Lambda Developer Guide: resource-based policies, read 16 Nov 2026
- AWS Service Authorization Reference, programmatic access (fetched 16 Nov 2026), read 16 Nov 2026
Last reviewed 16 Nov 2026.