AWS connect documentation change
Summary
Updated service name references from 'Amazon Connect' to 'Connect Customer' throughout the document, including section headers and policy examples
Security assessment
Changes involve branding updates only (renaming 'Amazon Connect' to 'Connect Customer'). No modifications to security guidance, policies, or vulnerability explanations. The confused deputy prevention content remains identical except for service names.
Diff
diff --git a/connect/latest/adminguide/cross-service-confused-deputy-prevention.md b/connect/latest/adminguide/cross-service-confused-deputy-prevention.md index d9fd6049b..75e24c41c 100644 --- a//connect/latest/adminguide/cross-service-confused-deputy-prevention.md +++ b//connect/latest/adminguide/cross-service-confused-deputy-prevention.md @@ -7 +7 @@ -Amazon Connect Customer ProfilesAmazon Connect Voice IDAmazon Connect chat message streaming cross-service confused deputy prevention +Connect Customer Customer ProfilesConnect Customer Voice IDConnect Customer chat message streaming cross-service confused deputy prevention @@ -13 +13 @@ The confused deputy problem is a security issue where an entity that doesn't hav -We recommend using the [`aws:SourceArn`](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourcearn) and [`aws:SourceAccount`](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourceaccount) global condition context keys in resource policies to limit the permissions that Amazon Connect gives another service to the resource. If you use both global condition context keys, the `aws:SourceAccount` value and the account in the `aws:SourceArn` value must use the same account ID when used in the same policy statement. +We recommend using the [`aws:SourceArn`](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourcearn) and [`aws:SourceAccount`](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourceaccount) global condition context keys in resource policies to limit the permissions that Connect Customer gives another service to the resource. If you use both global condition context keys, the `aws:SourceAccount` value and the account in the `aws:SourceArn` value must use the same account ID when used in the same policy statement. @@ -17 +17 @@ The most effective way to protect against the confused deputy problem is to use -## Amazon Connect Customer Profiles cross-service confused deputy prevention +## Connect Customer Customer Profiles cross-service confused deputy prevention @@ -19 +19 @@ The most effective way to protect against the confused deputy problem is to use -The following examples show policies that apply to cases where someone else is set up as the administrator for Amazon Connect Customer Profiles. Use these policies to prevent the confused deputy problem. +The following examples show policies that apply to cases where someone else is set up as the administrator for Connect Customer Customer Profiles. Use these policies to prevent the confused deputy problem. @@ -21 +21 @@ The following examples show policies that apply to cases where someone else is s -**Example Amazon Connect Customer Profiles policy to create Customer Profile domains** +**Example Connect Customer Customer Profiles policy to create Customer Profile domains** @@ -23 +23 @@ The following examples show policies that apply to cases where someone else is s -**Example Amazon Connect Customer Profiles policy to create Customer Profiles object types** +**Example Connect Customer Customer Profiles policy to create Customer Profiles object types** @@ -60 +60 @@ JSON -**Example Amazon Connect Customer Profiles policy to create and update dead-letter queues** +**Example Connect Customer Customer Profiles policy to create and update dead-letter queues** @@ -92 +92 @@ JSON -**Example Amazon Connect Customer Profiles policy to protect the Amazon S3 bucket used as part of the Identity Resolution process** +**Example Connect Customer Customer Profiles policy to protect the Amazon S3 bucket used as part of the Identity Resolution process** @@ -96 +96 @@ JSON - "Sid": "Allow Amazon Connect Customer Profiles to put S3 objects to your bucket", + "Sid": "Allow Connect Customer Customer Profiles to put S3 objects to your bucket", @@ -113 +113 @@ JSON -## Amazon Connect Voice ID cross-service confused deputy prevention +## Connect Customer Voice ID cross-service confused deputy prevention @@ -145 +145 @@ JSON -## Amazon Connect chat message streaming cross-service confused deputy prevention +## Connect Customer chat message streaming cross-service confused deputy prevention @@ -147 +147 @@ JSON -The following Amazon Connect example shows a resource policy to apply to prevent the confused deputy problem. +The following Connect Customer example shows a resource policy to apply to prevent the confused deputy problem.