AWS appfabric documentation change
Summary
Removed mention of default inability to use AWS Management Console/CLI/API and simplified default permission explanation
Security assessment
The change removes specific details about default access restrictions but maintains the core concept of IAM permissions. This appears to be a documentation simplification rather than addressing a specific security vulnerability or weakness. The update focuses on clarity rather than introducing new security controls or mitigating identified risks.
Diff
diff --git a/appfabric/latest/adminguide/security_iam_id-based-policy-examples.md b/appfabric/latest/adminguide/security_iam_id-based-policy-examples.md index ce892605f..fadf7bd79 100644 --- a//appfabric/latest/adminguide/security_iam_id-based-policy-examples.md +++ b//appfabric/latest/adminguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAppFabric for security IAM policy examples -By default, users and roles don't have permission to create or modify AppFabric 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 AppFabric resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.