AWS simspaceweaver documentation change
Summary
Removed redundant statement about default inability to use AWS console/CLI/API and streamlined policy explanation
Security assessment
The change simplifies existing IAM policy documentation without introducing new security controls or addressing specific vulnerabilities. While IAM policies are security-related, this edit appears to be a clarification/removal of redundant information rather than a response to a security issue. No evidence of vulnerability mitigation.
Diff
diff --git a/simspaceweaver/1.15/userguide/security_iam_id-based-policy-examples.md b/simspaceweaver/1.15/userguide/security_iam_id-based-policy-examples.md index c82fa7a13..504942f4e 100644 --- a//simspaceweaver/1.15/userguide/security_iam_id-based-policy-examples.md +++ b//simspaceweaver/1.15/userguide/security_iam_id-based-policy-examples.md @@ -11 +11 @@ End of support notice: On May 20, 2026, AWS will end support for AWS SimSpace We -By default, users and roles don't have permission to create or modify SimSpace Weaver 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 SimSpace Weaver resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.