AWS migrationhub-strategy documentation change
Summary
Removed specific mention of AWS Management Console, CLI, and API from default permissions explanation
Security assessment
The change simplifies the description of default permissions but does not address any specific vulnerability or security incident. While IAM policies are security-related, this edit appears to be a clarification/streamlining of existing documentation rather than a response to a security issue or addition of security features.
Diff
diff --git a/migrationhub-strategy/latest/userguide/security_iam_id-based-policy-examples.md b/migrationhub-strategy/latest/userguide/security_iam_id-based-policy-examples.md index c419185e1..4af56948a 100644 --- a//migrationhub-strategy/latest/userguide/security_iam_id-based-policy-examples.md +++ b//migrationhub-strategy/latest/userguide/security_iam_id-based-policy-examples.md @@ -11 +11 @@ AWS Migration Hub will no longer be open to new customers starting November 7, 2 -By default, users and roles don't have permission to create or modify Strategy Recommendations 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 Strategy Recommendations resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.