AWS appflow documentation change
Summary
Simplified introductory paragraph about IAM permissions for Amazon AppFlow by removing specific references to AWS Management Console, CLI, and API access limitations
Security assessment
The change removes explanatory text about default access restrictions but does not address any specific security vulnerability or weakness. This appears to be an editorial simplification rather than a security-related update.
Diff
diff --git a/appflow/latest/userguide/security_iam_id-based-policy-examples.md b/appflow/latest/userguide/security_iam_id-based-policy-examples.md index 284e77e31..42ada8ae1 100644 --- a//appflow/latest/userguide/security_iam_id-based-policy-examples.md +++ b//appflow/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesExample 1: Allow full administrator accessExample 2: Allow -By default, users and roles don't have permission to create or modify Amazon AppFlow 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 Amazon AppFlow resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.