AWS managed-blockchain documentation change
Summary
Changed 'AWS CloudFormation' to 'CloudFormation' in IAM policy documentation
Security assessment
Cosmetic change to service name formatting. No modifications to security guidance or evidence of addressing vulnerabilities.
Diff
diff --git a/managed-blockchain/latest/ethereum-dev/security_iam_id-based-policy-examples.md b/managed-blockchain/latest/ethereum-dev/security_iam_id-based-policy-examples.md index 004ff925a..07c5669f6 100644 --- a//managed-blockchain/latest/ethereum-dev/security_iam_id-based-policy-examples.md +++ b//managed-blockchain/latest/ethereum-dev/security_iam_id-based-policy-examples.md @@ -38 +38 @@ 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_.