AWS connect documentation change
Summary
Rebranded 'Amazon Connect' to 'Connect Customer' throughout the documentation, including console references, domain naming, and feature descriptions. Updated screenshots and headings to reflect the new naming convention.
Security assessment
The changes are purely branding/naming updates without any modifications to security configurations, vulnerability disclosures, or security features. All technical steps (SES production mode, S3 bucket setup, CORS policies) remain unchanged. No evidence of security vulnerability fixes or new security capabilities.
Diff
diff --git a/connect/latest/adminguide/enable-email1.md b/connect/latest/adminguide/enable-email1.md index e532a6c7d..63b392144 100644 --- a//connect/latest/adminguide/enable-email1.md +++ b//connect/latest/adminguide/enable-email1.md @@ -7 +7 @@ -Step 1: Move Amazon SES into production modeStep 2: Get a default Amazon Connect email domain(Optional) Step 3: Use custom email domainsStep 4: Enable email and create an Amazon S3 bucketStep 5: Configure a CORS policyNext stepsAPIs to enable email +Step 1: Move Amazon SES into production modeStep 2: Get a default Connect Customer email domain(Optional) Step 3: Use custom email domainsStep 4: Enable email and create an Amazon S3 bucketStep 5: Configure a CORS policyNext stepsAPIs to enable email @@ -9 +9 @@ Step 1: Move Amazon SES into production modeStep 2: Get a default Amazon Connect -# Enable email for your Amazon Connect instance +# Enable email for your Connect Customer instance @@ -11 +11 @@ Step 1: Move Amazon SES into production modeStep 2: Get a default Amazon Connect -This topic is for administrators who have access to the Amazon Connect console. It explains how to enable email for your instance using the Amazon Connect admin website. For a list of the APIs to enable email programmatically, see APIs to enable email. +This topic is for administrators who have access to the Connect Customer console. It explains how to enable email for your instance using the Connect Customer admin website. For a list of the APIs to enable email programmatically, see APIs to enable email. @@ -15 +15 @@ When you enable email, you get an auto-generated email domain. Optionally, you c - * **Amazon Connect email domain**. The email domain is _`instance-alias`.email.connect.aws_. + * **Connect Customer email domain**. The email domain is _`instance-alias`.email.connect.aws_. @@ -19 +19 @@ When you enable email, you get an auto-generated email domain. Optionally, you c - * Or, you can use this email domain to integrate with Amazon Connect and start receiving emails into Amazon Connect. For example, if you have an email address such as [email protected]_ you can forward email into Amazon Connect by using [email protected]_. + * Or, you can use this email domain to integrate with Connect Customer and start receiving emails into Connect Customer. For example, if you have an email address such as [email protected]_ you can forward email into Connect Customer by using [email protected]_. @@ -28 +28 @@ When you enable email, you get an auto-generated email domain. Optionally, you c -Amazon Connect uses Amazon SES for sending and receiving emails. If you have a new Amazon SES instance, you need to take it out of sandbox mode. For instructions, see [Request production access (Moving out of the Amazon SES sandbox)](https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html) in the _Amazon SES Developer Guide_. +Connect Customer uses Amazon SES for sending and receiving emails. If you have a new Amazon SES instance, you need to take it out of sandbox mode. For instructions, see [Request production access (Moving out of the Amazon SES sandbox)](https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html) in the _Amazon SES Developer Guide_. @@ -30 +30 @@ Amazon Connect uses Amazon SES for sending and receiving emails. If you have a n -After you move Amazon SES into production mode, if you already enabled email when you created your Amazon Connect instance, skip to these topics: +After you move Amazon SES into production mode, if you already enabled email when you created your Connect Customer instance, skip to these topics: @@ -39 +39 @@ After you move Amazon SES into production mode, if you already enabled email whe -## Step 2: Get a default Amazon Connect email domain +## Step 2: Get a default Connect Customer email domain @@ -41 +41 @@ After you move Amazon SES into production mode, if you already enabled email whe -These steps only apply if you already created an Amazon Connect instance but didn't enable email. Complete these steps to get a default email domain from Amazon Connect. +These steps only apply if you already created an Connect Customer instance but didn't enable email. Complete these steps to get a default email domain from Connect Customer. @@ -43 +43 @@ These steps only apply if you already created an Amazon Connect instance but did - 1. In the Amazon Connect console, on the left navigation menu, choose **Email** , and then choose **Create service role**. This role needs to be created only once for your account. It allows Amazon SES to route emails to Amazon Connect. + 1. In the Connect Customer console, on the left navigation menu, choose **Email** , and then choose **Create service role**. This role needs to be created only once for your account. It allows Amazon SES to route emails to Connect Customer. @@ -49 +49 @@ These steps only apply if you already created an Amazon Connect instance but did - 3. In the **Add email domain** box, choose **Amazon Connect email domain** , as shown in the following image. When you choose this option, the name of the domain is auto-generated: _`instance-alias`.email.connect.aws_. You cannot change this email address. + 3. In the **Add email domain** box, choose **Connect Customer email domain** , as shown in the following image. When you choose this option, the name of the domain is auto-generated: _`instance-alias`.email.connect.aws_. You cannot change this email address. @@ -51 +51 @@ These steps only apply if you already created an Amazon Connect instance but did - + @@ -60 +60 @@ You can import up to five custom domains that have been [onboarded to Amazon SES - 1. In the Amazon Connect console, on the left navigation menu, choose **Email** , and then choose **Add Domain** as shown in the following image. + 1. In the Connect Customer console, on the left navigation menu, choose **Email** , and then choose **Add Domain** as shown in the following image. @@ -62 +62 @@ You can import up to five custom domains that have been [onboarded to Amazon SES - + @@ -73 +73 @@ You can import up to five custom domains that have been [onboarded to Amazon SES -These steps apply only if you already created an Amazon Connect instance but didn't enable email. +These steps apply only if you already created an Connect Customer instance but didn't enable email. @@ -81 +81 @@ If you choose **Enable Attachments sharing** for your instance, you must create - 1. Open the Amazon Connect console at [https://console.aws.amazon.com/connect/](https://console.aws.amazon.com/connect/). + 1. Open the Connect Customer console at [https://console.aws.amazon.com/connect/](https://console.aws.amazon.com/connect/). @@ -83 +83 @@ If you choose **Enable Attachments sharing** for your instance, you must create - 2. On the instances page, choose the instance alias. The instance alias is also your **instance name** , which appears in your Amazon Connect URL. The following image shows the **Amazon Connect virtual contact center instances** page, with a box around the instance alias. + 2. On the instances page, choose the instance alias. The instance alias is also your **instance name** , which appears in your Connect Customer URL. The following image shows the **Connect Customer virtual contact center instances** page, with a box around the instance alias. @@ -85 +85 @@ If you choose **Enable Attachments sharing** for your instance, you must create - + @@ -110 +110 @@ To allow customers and agents to upload and download files, update your cross-or - 1. Open the Amazon Connect console at [https://console.aws.amazon.com/connect/](https://console.aws.amazon.com/connect/). + 1. Open the Connect Customer console at [https://console.aws.amazon.com/connect/](https://console.aws.amazon.com/connect/). @@ -112 +112 @@ To allow customers and agents to upload and download files, update your cross-or - 2. In the Amazon Connect console, choose **Data storage** , and locate the Amazon S3 bucket name. + 2. In the Connect Customer console, choose **Data storage** , and locate the Amazon S3 bucket name. @@ -167 +167 @@ Your CORS policy may look similar to the following example: - * [Set up attachment scanning in Amazon Connect](./setup-attachment-scanning.html): This topic is for developers who are familiar with Lambda. You can configure Amazon Connect to scan email attachments by using your preferred scanning application. + * [Set up attachment scanning in Connect Customer](./setup-attachment-scanning.html): This topic is for developers who are familiar with Lambda. You can configure Connect Customer to scan email attachments by using your preferred scanning application. @@ -191 +191 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -How Amazon Connect email works +How Connect Customer email works