AWS directconnect documentation change
Summary
Updated service name reference from 'AWS Direct Connect' to 'Direct Connect' in policy example description
Security assessment
Change is a terminology update without altering the security policy logic, conditions, or permissions. The resource-based policy example remains functionally identical with no security implications.
Diff
diff --git a/directconnect/latest/UserGuide/security_iam_resource-based-policy-examples.md b/directconnect/latest/UserGuide/security_iam_resource-based-policy-examples.md index 4d9e6e038..18c6ebdca 100644 --- a//directconnect/latest/UserGuide/security_iam_resource-based-policy-examples.md +++ b//directconnect/latest/UserGuide/security_iam_resource-based-policy-examples.md @@ -53 +53 @@ JSON -You can use conditions in your IAM policies to control which tag key–value pairs can be passed in a request that tags an AWS resource. The following example shows how you might create a policy that allows using the AWS Direct Connect TagResource action to attach tags to a virtual interface only if the tag contains the environment key and the preprod or production values. As a best practice, use the `ForAllValues` modifier with the `aws:TagKeys` condition key to indicate that only the key environment is allowed in the request. +You can use conditions in your IAM policies to control which tag key–value pairs can be passed in a request that tags an AWS resource. The following example shows how you might create a policy that allows using the Direct Connect TagResource action to attach tags to a virtual interface only if the tag contains the environment key and the preprod or production values. As a best practice, use the `ForAllValues` modifier with the `aws:TagKeys` condition key to indicate that only the key environment is allowed in the request.