AWS managed-flink documentation change
Summary
Removed redundant explanation about access methods (Console/CLI/API) and role assumption process from IAM policy introduction
Security assessment
Simplifies introductory text without changing security meaning. No evidence of addressing vulnerabilities or modifying security controls.
Diff
diff --git a/managed-flink/latest/java/security_iam_id-based-policy-examples.md b/managed-flink/latest/java/security_iam_id-based-policy-examples.md index 2c61256c1..23fcc8673 100644 --- a//managed-flink/latest/java/security_iam_id-based-policy-examples.md +++ b//managed-flink/latest/java/security_iam_id-based-policy-examples.md @@ -11 +11 @@ Amazon Managed Service for Apache Flink (Amazon MSF) was previously known as Ama -By default, users and roles don't have permission to create or modify Managed Service for Apache Flink 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 Managed Service for Apache Flink resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.