AWS managed-flink documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in IAM policy condition example.
Security assessment
Naming convention update without modifying policy structure or security recommendations. IAM condition logic remains functionally identical.
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 23fcc8673..4dd399fb6 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 @@ -36 +36 @@ Identity-based policies determine whether someone can create, access, or delete - * **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as AWS CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the _IAM User Guide_. + * **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the _IAM User Guide_.