AWS iot-sitewise documentation change
Summary
Updated reference from 'AWS CloudFormation' to 'CloudFormation' in IAM policy conditions section
Security assessment
Consistency update in service naming without modifying security recommendations. Existing security guidance about policy conditions remains unchanged.
Diff
diff --git a/iot-sitewise/latest/userguide/security_iam_id-based-policy-examples.md b/iot-sitewise/latest/userguide/security_iam_id-based-policy-examples.md index 0103eb76b..a8f2a1831 100644 --- a//iot-sitewise/latest/userguide/security_iam_id-based-policy-examples.md +++ b//iot-sitewise/latest/userguide/security_iam_id-based-policy-examples.md @@ -43 +43 @@ 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_.