AWS migrationhub-refactor-spaces documentation change
Summary
Removed mention of specific interfaces (AWS Console/CLI/API) being blocked by default permissions, focusing on core permission requirements.
Security assessment
The change simplifies the explanation of default permissions but does not address any specific vulnerability or security incident. While it removes explicit references to blocked interfaces, the core security guidance about requiring IAM policies remains intact.
Diff
diff --git a/migrationhub-refactor-spaces/latest/userguide/security_iam_id-based-policy-examples.md b/migrationhub-refactor-spaces/latest/userguide/security_iam_id-based-policy-examples.md index ccea4b12f..a2f71c67f 100644 --- a//migrationhub-refactor-spaces/latest/userguide/security_iam_id-based-policy-examples.md +++ b//migrationhub-refactor-spaces/latest/userguide/security_iam_id-based-policy-examples.md @@ -11 +11 @@ AWS Migration Hub Refactor Spaces will no longer be open to new customers starti -By default, users and roles don't have permission to create or modify Refactor Spaces 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 Refactor Spaces resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.