# Lambda functions now accept full IAM resource-based policies

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

AWS announced on 25 August 2026 that Lambda functions support full IAM resource-based policies. One policy document can cover multiple principals and actions and use the full range of IAM condition keys, such as source IP or principal tag, instead of adding permissions one principal at a time.

AWS Lambda functions now support full IAM resource-based policies, according to an announcement dated 25 August 2026. AWS says platform admins and security teams can define permissions for multiple principals and actions in a single policy document and use the full range of IAM condition keys. Previously, Lambda required permissions to be added individually per principal, which limited flexibility at scale.

AWS gives examples of restricting access by source IP or principal tag and allowing several services to invoke a function with one policy. Policies can be updated in one step in the console, CLI, SDKs, CloudFormation or SAM, in all commercial Regions at no extra charge. For resource-level guardrails, conditions can now be written on Lambda the same way as on other services.

## Related pages

- [IAM raises the default managed policies per role from 10 to 20](/news/iam-managed-policies-per-role-default-20/)
- [VPC Service Controls recommender flags perimeter gaps in preview](/news/vpc-sc-recommender-perimeter-optimization-preview/)
- [S3 access denied errors now name the SCP or RCP behind the deny](/news/s3-access-denied-messages-name-scp-rcp-policy/)
- [All of them](/news/)

## Sources

- https://aws.amazon.com/about-aws/whats-new/2026/08/aws-lambda-full-iam-resource-based-policies/ (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/news/lambda-full-iam-resource-based-policies/
