AWS simspaceweaver documentation change
Summary
Removed specific mention of inability to use AWS Management Console, CLI, or API without permissions while retaining core statement about default permissions.
Security assessment
The change simplifies the explanation of default permissions but does not address a specific security vulnerability or weakness. The core security principle (default deny) remains intact. The removal of specific examples (Console/CLI/API) does not introduce or mitigate security risks.
Diff
diff --git a/simspaceweaver/1.16/userguide/security_iam_id-based-policy-examples.md b/simspaceweaver/1.16/userguide/security_iam_id-based-policy-examples.md index 0c81d9beb..a7615e6b7 100644 --- a//simspaceweaver/1.16/userguide/security_iam_id-based-policy-examples.md +++ b//simspaceweaver/1.16/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.