AWS social-messaging documentation change
Summary
Updated terminology from 'Amazon Connect instance' to 'Connect Customer instance' throughout the document.
Security assessment
Changes are purely branding/nomenclature updates without any security implications. No security vulnerabilities, configurations, or features were modified or added.
Diff
diff --git a/social-messaging/latest/userguide/managing-phone-numbers-add.md b/social-messaging/latest/userguide/managing-phone-numbers-add.md index 4c1f7af73..b74608b50 100644 --- a//social-messaging/latest/userguide/managing-phone-numbers-add.md +++ b//social-messaging/latest/userguide/managing-phone-numbers-add.md @@ -24 +24 @@ Before you begin, the following prerequisites must be met: -The following prerequisites must be met to use either an Amazon SNS topic or Amazon Connect instance as a message and event destination. +The following prerequisites must be met to use either an Amazon SNS topic or Connect Customer instance as a message and event destination. @@ -39 +39 @@ Amazon SNS FIFO topics are not supported. -###### Amazon Connect instance +###### Connect Customer instance @@ -41 +41 @@ Amazon SNS FIFO topics are not supported. - * An Amazon Connect instances has been [created](https://docs.aws.amazon.com/connect/latest/adminguide/tutorial1-set-up-your-instance.html) and [permissions](./managing-event-destinations-add.html#managing-event-destinations-amazon-connect-policies) have been added. + * An Connect Customer instances has been [created](https://docs.aws.amazon.com/connect/latest/adminguide/tutorial1-set-up-your-instance.html) and [permissions](./managing-event-destinations-add.html#managing-event-destinations-amazon-connect-policies) have been added. @@ -88 +88 @@ In the **Message and event destination details** section, turn on **Event publis - 13. For **Destination type** choose either Amazon SNS or Amazon Connect + 13. For **Destination type** choose either Amazon SNS or Connect Customer @@ -92 +92 @@ In the **Message and event destination details** section, turn on **Event publis - 2. For Amazon Connect + 2. For Connect Customer @@ -98 +98 @@ In the **Message and event destination details** section, turn on **Event publis - 1. **Choose existing IAM role** – Choose an existing IAM policy from the **Existing IAM roles** drop down. For example IAM policies, see [IAM policies for Amazon Connect](./managing-event-destinations-add.html#managing-event-destinations-amazon-connect-policies). + 1. **Choose existing IAM role** – Choose an existing IAM policy from the **Existing IAM roles** drop down. For example IAM policies, see [IAM policies for Connect Customer](./managing-event-destinations-add.html#managing-event-destinations-amazon-connect-policies). @@ -100 +100 @@ In the **Message and event destination details** section, turn on **Event publis - 2. **Enter IAM role ARN** – Enter the ARN of the IAM policy into **Use existing IAM role Arn**. For example IAM policies, see [IAM policies for Amazon Connect](./managing-event-destinations-add.html#managing-event-destinations-amazon-connect-policies). + 2. **Enter IAM role ARN** – Enter the ARN of the IAM policy into **Use existing IAM role Arn**. For example IAM policies, see [IAM policies for Connect Customer](./managing-event-destinations-add.html#managing-event-destinations-amazon-connect-policies).