AWS connect documentation change
Summary
Updated documentation to clarify console navigation paths for enabling logging features and adjusted storage location descriptions for automated interaction logs.
Security assessment
Changes focus on improving clarity about where settings are configured in the console and where logs are stored. No explicit security vulnerabilities, mitigations, or new security features are mentioned.
Diff
diff --git a/connect/latest/adminguide/about-contact-flow-logs.md b/connect/latest/adminguide/about-contact-flow-logs.md index f49e57d65..80fae8573 100644 --- a//connect/latest/adminguide/about-contact-flow-logs.md +++ b//connect/latest/adminguide/about-contact-flow-logs.md @@ -15 +15 @@ Flow logs help you track customers between different flows by including the ID o -The CloudWatch group log is created automatically when [Enable flow logging](./contact-flow-logs.html#enable-contact-flow-logs) is selected for your instance. However, to enable logging, you also need to add a **Set logging behavior** block to your flow. For instructions, see [Enable Amazon Connect flow logs in an Amazon CloudWatch log group](./contact-flow-logs.html). +The CloudWatch group log is created automatically when [Enable flow logging](./contact-flow-logs.html#enable-contact-flow-logs) is selected for your instance on the Amazon Connect console. However, to enable logging, you also need to add a **Set logging behavior** block to your flow. For instructions, see [Enable Amazon Connect flow logs in an Amazon CloudWatch log group](./contact-flow-logs.html). @@ -19 +19 @@ The CloudWatch group log is created automatically when [Enable flow logging](./c -These logs are saved in an S3 bucket that is created when you [select](./monitor-automated-interaction-logs.html) the following options for your instance: +These logs are saved in an S3 bucket that is created when you [select](./monitor-automated-interaction-logs.html) the following options for your instance on the Amazon Connect console: @@ -21 +21 @@ These logs are saved in an S3 bucket that is created when you [select](./monitor - * **Enable Bot Analytics and Transcripts in Amazon Connect**. Choose to generate a log of the full bot transcript. The transcript is then available for you to read on the **Contact details** page. + * **Enable call recording** and create or select your S3 bucket on the **Data storage** page. The automated interaction log is stored in the same S3 location as that of your call recording. @@ -23 +23 @@ These logs are saved in an S3 bucket that is created when you [select](./monitor - * **Enable Automated Interaction Logs**. Choose to log key interaction points such as flows, prompts, menus, and keypad selections. This automated log is available on the **Contact details** page. You can see where errors have occurred such as customer timeouts or Lambda function errors. + * **Enable Automated Interaction Logs** on the **Flows** page. This option enables the logging of key interaction points such as flows, prompts, menus, and keypad selections. This automated log is available in your S3 storage and in the **Contact details** page on the Amazon Connect admin website. @@ -25 +25 @@ These logs are saved in an S3 bucket that is created when you [select](./monitor - * **Enable call recording**. Choose this option on the **Data storage** page. It enables you to listen to the call recording on the **Contact details** page while viewing the transcript of the automated interaction. + * **Enable Bot Analytics and Transcripts** in Amazon Connect on the **Flows** page. This option ensures the log includes the Amazon Lex bot transcript.