AWS forecast documentation change
Summary
Removed redundant statement about default permissions and simplified explanation of IAM policy assignment process.
Security assessment
The change removes a redundant explanation of default permissions (users can't perform tasks via console/CLI/API) and simplifies the policy assignment process description. While the topic relates to IAM security, there is no evidence of addressing a specific vulnerability or weakness. The edit appears to be a routine documentation clarification rather than a security fix.
Diff
diff --git a/forecast/latest/dg/security_iam_id-based-policy-examples.md b/forecast/latest/dg/security_iam_id-based-policy-examples.md index 0b889697f..c847d3e8a 100644 --- a//forecast/latest/dg/security_iam_id-based-policy-examples.md +++ b//forecast/latest/dg/security_iam_id-based-policy-examples.md @@ -11 +11 @@ Amazon Forecast is no longer available to new customers. Existing customers of A -By default, users and roles don't have permission to create or modify Forecast 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 Forecast resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.