AWS connect documentation change
Summary
Renamed all references from 'Amazon Connect' to 'Connect Customer' throughout the document, including section headers, descriptions, console references, and images. Updated terminology for consistency.
Security assessment
This is purely a branding/terminology change with no modifications to security configurations, permissions, or security-related content. The Lambda permission requirements (principal: connect.amazonaws.com) remain unchanged. No vulnerabilities or security enhancements are mentioned.
Diff
diff --git a/connect/latest/adminguide/connect-lambda-functions.md b/connect/latest/adminguide/connect-lambda-functions.md index 1ed6472d7..94ba73f1b 100644 --- a//connect/latest/adminguide/connect-lambda-functions.md +++ b//connect/latest/adminguide/connect-lambda-functions.md @@ -9 +9 @@ Create a Lambda functionAdd a function to your instanceInvoke a Lambda from a fl -# Grant Amazon Connect access to your AWS Lambda functions +# Grant Connect Customer access to your AWS Lambda functions @@ -11 +11 @@ Create a Lambda functionAdd a function to your instanceInvoke a Lambda from a fl -Amazon Connect can interact with your own systems and take different paths in flows dynamically. To achieve this, invoke AWS Lambda functions in a flow, fetch the results, and call your own services or interact with other AWS data stores or services. For more information, see the [AWS Lambda Developer Guide](https://docs.aws.amazon.com/lambda/latest/dg/). +Connect Customer can interact with your own systems and take different paths in flows dynamically. To achieve this, invoke AWS Lambda functions in a flow, fetch the results, and call your own services or interact with other AWS data stores or services. For more information, see the [AWS Lambda Developer Guide](https://docs.aws.amazon.com/lambda/latest/dg/). @@ -19 +19 @@ To invoke a Lambda function from a flow, complete the following tasks. - * Add a Lambda function to your Amazon Connect instance + * Add a Lambda function to your Connect Customer instance @@ -40 +40 @@ Create a Lambda function, using any runtime, and configure it. For more informat -If you create the Lambda function in the same Region as your contact center, you can use the Amazon Connect console to add the Lambda function to your instance as described in the next task, Add a Lambda function to your Amazon Connect instance. This automatically adds resource permissions that allow Amazon Connect to invoke the Lambda function. Otherwise, if the Lambda function is in a different Region, you can add it to your flow using the flow designer and add the resource permissions using the [add-permission](https://docs.aws.amazon.com/cli/latest/reference/lambda/add-permission.html) command, with a principal of `connect.amazonaws.com` and the ARN of your Amazon Connect instance. For more information, see [Using Resource-Based Policies for AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/access-control-resource-based.html) in the _AWS Lambda Developer Guide_. +If you create the Lambda function in the same Region as your contact center, you can use the Connect Customer console to add the Lambda function to your instance as described in the next task, Add a Lambda function to your Connect Customer instance. This automatically adds resource permissions that allow Connect Customer to invoke the Lambda function. Otherwise, if the Lambda function is in a different Region, you can add it to your flow using the flow designer and add the resource permissions using the [add-permission](https://docs.aws.amazon.com/cli/latest/reference/lambda/add-permission.html) command, with a principal of `connect.amazonaws.com` and the ARN of your Connect Customer instance. For more information, see [Using Resource-Based Policies for AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/access-control-resource-based.html) in the _AWS Lambda Developer Guide_. @@ -42 +42 @@ If you create the Lambda function in the same Region as your contact center, you -## Add a Lambda function to your Amazon Connect instance +## Add a Lambda function to your Connect Customer instance @@ -44 +44 @@ If you create the Lambda function in the same Region as your contact center, you -Before you can use an Lambda function in a flow, you need to add it to your Amazon Connect instance. +Before you can use an Lambda function in a flow, you need to add it to your Connect Customer instance. @@ -48 +48 @@ Before you can use an Lambda function in a flow, you need to add it to your Amaz - 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/). @@ -50 +50 @@ Before you can use an Lambda function in a flow, you need to add it to your Amaz - 2. On the instances page, choose your instance name in the **Instance Alias** column. This instance name appears in the URL you use to access Amazon Connect. + 2. On the instances page, choose your instance name in the **Instance Alias** column. This instance name appears in the URL you use to access Connect Customer. @@ -52 +52 @@ Before you can use an Lambda function in a flow, you need to add it to your Amaz - + @@ -161 +161 @@ The request is divided into two parts: - * Contact data—This is always passed by Amazon Connect for every contact. Some parameters are optional. + * Contact data—This is always passed by Connect Customer for every contact. Some parameters are optional. @@ -194 +194 @@ If your Lambda invocation in a flow gets throttled, the request will be retried. -When a synchronous invocation returns an error, Amazon Connect retries up to 3 times, for a maximum of 8 seconds. At that point, the flow will progress down the Error branch. +When a synchronous invocation returns an error, Connect Customer retries up to 3 times, for a maximum of 8 seconds. At that point, the flow will progress down the Error branch. @@ -200 +200 @@ To learn more about how Lambda retries, see [Error Handling and Automatic Retrie -Amazon Connect limits the duration of a sequence of Lambda functions to 20 seconds. It times out with an error message when the total execution time exceeds this threshold. Because customers hear silence while a Lambda function runs, we recommend adding a **Play prompt** block between functions to keep them engaged during the long interaction. +Connect Customer limits the duration of a sequence of Lambda functions to 20 seconds. It times out with an error message when the total execution time exceeds this threshold. Because customers hear silence while a Lambda function runs, we recommend adding a **Play prompt** block between functions to keep them engaged during the long interaction. @@ -206 +206 @@ By breaking up a chain of Lambda functions with the **Play prompt** block, you c -To successfully pass attributes and parameters between your Lambda function and Amazon Connect, configure your function to correctly parse the JSON request sent from the **Invoke AWS Lambda function** block or **Set contact attributes** , and define any business logic that should be applied. How the JSON is parsed depends on the runtime you use for your function. +To successfully pass attributes and parameters between your Lambda function and Connect Customer, configure your function to correctly parse the JSON request sent from the **Invoke AWS Lambda function** block or **Set contact attributes** , and define any business logic that should be applied. How the JSON is parsed depends on the runtime you use for your function. @@ -238 +238 @@ The Lambda response can be up to 32kb. If you fail to reach Lambda, the function -Test the output returned from your Lambda function to confirm that it will be correctly consumed when returned to Amazon Connect. The following example shows a sample response in Node.JS: +Test the output returned from your Lambda function to confirm that it will be correctly consumed when returned to Connect Customer. The following example shows a sample response in Node.JS: @@ -429 +429 @@ Your balance will be different. The code generates a random number. -### Step 2: Add your Lambda to Amazon Connect +### Step 2: Add your Lambda to Connect Customer @@ -431 +431 @@ Your balance will be different. The code generates a random number. - 1. Go to the Amazon Connect console, at [https://console.aws.amazon.com/connect/](https://console.aws.amazon.com/connect/). + 1. Go to the Connect Customer console, at [https://console.aws.amazon.com/connect/](https://console.aws.amazon.com/connect/). @@ -433 +433 @@ Your balance will be different. The code generates a random number. - 2. Choose your Amazon Connect instance alias. + 2. Choose your Connect Customer instance alias. @@ -435 +435 @@ Your balance will be different. The code generates a random number. - + @@ -454 +454 @@ The following image is an example of the flow you are going to build using the s - 1. Log in to the Amazon Connect admin website at https://`instance name`.my.connect.aws/. + 1. Log in to the Connect Customer admin website at https://`instance name`.my.connect.aws/.