AWS lambda documentation change
Summary
Shortened explanation about default permissions, removing references to console/CLI/API access limitations
Security assessment
The change simplifies documentation about IAM policy defaults without altering security guidance. The removed text about interface restrictions was redundant with the broader statement about resource permissions, and there's no indication of a security vulnerability being addressed.
Diff
diff --git a/lambda/latest/dg/security_iam_id-based-policy-examples.md b/lambda/latest/dg/security_iam_id-based-policy-examples.md index 48bfaf641..f89b4cc18 100644 --- a//lambda/latest/dg/security_iam_id-based-policy-examples.md +++ b//lambda/latest/dg/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify Lambda resources. They also can't perform tasks by using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. +By default, users and roles don't have permission to create or modify Lambda resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.