AWS amplify documentation change
Summary
Removed mention of default inability to perform tasks via AWS Console/CLI/API and simplified explanation of IAM policy requirements
Security assessment
The change removes redundant information about default permissions but does not address any specific security vulnerability or weakness. It maintains existing security documentation about IAM policies without introducing new security-related content.
Diff
diff --git a/amplify/latest/userguide/security_iam_id-based-policy-examples.md b/amplify/latest/userguide/security_iam_id-based-policy-examples.md index fe5494fba..bf1dfb2f4 100644 --- a//amplify/latest/userguide/security_iam_id-based-policy-examples.md +++ b//amplify/latest/userguide/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 Amplify 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 Amplify resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.