AWS proton documentation change
Summary
Removed mention of specific access methods (AWS Management Console, CLI, API) being blocked by default permissions, while retaining core explanation about IAM policy requirements.
Security assessment
The change simplifies the default permissions explanation but doesn't introduce new security-related information or address a specific vulnerability. The core security concept (default deny + need for explicit IAM policies) remains unchanged.
Diff
diff --git a/proton/latest/userguide/security_iam_id-based-policy-examples.md b/proton/latest/userguide/security_iam_id-based-policy-examples.md index 9b6946086..f18beaef8 100644 --- a//proton/latest/userguide/security_iam_id-based-policy-examples.md +++ b//proton/latest/userguide/security_iam_id-based-policy-examples.md @@ -11 +11 @@ End of support notice: On October 7, 2026, AWS will end support for AWS Proton. -By default, users and roles don't have permission to create or modify AWS Proton 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 AWS Proton resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.