AWS connect documentation change
Summary
Updated documentation for AI agent traces feature: Added section headers, rephrased enablement steps, added migration note for existing users, expanded permission requirements, modified UI terminology, and added reference to AI agent traces documentation.
Security assessment
The changes primarily document a new feature (AI agent traces) without addressing vulnerabilities. Security relevance comes from explicitly adding 'AI agent traces' to permission requirements for unredacted transcripts, highlighting access control considerations for new telemetry data.
Diff
diff --git a/connect/latest/adminguide/monitor-automated-interaction-logs.md b/connect/latest/adminguide/monitor-automated-interaction-logs.md index 6cc367b0c..af894176f 100644 --- a//connect/latest/adminguide/monitor-automated-interaction-logs.md +++ b//connect/latest/adminguide/monitor-automated-interaction-logs.md @@ -38 +38 @@ Currently, Connect Customer doesn’t support S3 buckets with [Object Lock](http - 4. Select **Enable Bot Analytics and Transcripts in Connect Customer**. Choose this option to log a full transcript of the Amazon Lex portion of the customer's experience. The transcript is then available for you to read on the **Contact details** page. + 4. Under the **Amazon Lex Bots** section, select **Enable Bot Analytics and Transcripts in Amazon Connect**. Choose this option to log a full transcript of the Amazon Lex portion of the customer's experience. The transcript and traces is then available for you to read on the **Contact details** page. @@ -40 +40,5 @@ Currently, Connect Customer doesn’t support S3 buckets with [Object Lock](http - 5. Select **Enable automated interaction logs**. Choose this option to log key interaction points such as flows, prompts, menus, and keypad selections. The can view the interaction log, and a listen to the audio recording if available, on the **Contact details** page. +###### Note + +If you previously enabled **Bot Analytics and Transcripts in Amazon Connect** (prior to June 5, 2026), you must disable and re-enable this setting to activate the AI agent traces feature. + + 5. Under the **Automated interaction logs** section, select **Enable Automated Interaction Logs**. This enables you to view Flow details, Lex bot, and AI agent traces on the **Contact details** page. @@ -51 +55 @@ To keep customer data secure, you can set up permissions to have granular contro - * **Analytics and Optimization** \- **Automated interaction voice (IVR) transcripts (unredacted)** permissions: These permissions are required to access logs of the IVR interaction such as keypad inputs in response to IVR prompts, transcripts of Lex interactions, and more. + * **Analytics and Optimization** \- **Automated interaction voice (IVR) transcripts (unredacted)** permissions: These permissions are required to access logs of the IVR interaction such as keypad inputs in response to IVR prompts, transcripts of Lex interactions, AI agent traces and more. @@ -66 +70 @@ The following image shows an example of an automated interaction log on the **Co - 2. Choose **Show flow details** to hide system details about the flows and flow blocks. + 2. Choose **Show flow & trace details** to show or hide system details about the flows and flow blocks. @@ -79,0 +84,2 @@ If no audio recording is available, there is no option to play the prompt. + 7. To learn more about enabling AI agent traces, see [AI agent traces](./ai-agent-traces.html). +