AWS connect documentation change
Summary
Updated product name references from 'Amazon Connect' to 'Connect Customer' in flow logging documentation
Security assessment
Changes are limited to product name rebranding. Logging functionality, security controls, and storage mechanisms (CloudWatch, S3) remain unchanged. No new security features or vulnerability fixes are introduced.
Diff
diff --git a/connect/latest/adminguide/about-contact-flow-logs.md b/connect/latest/adminguide/about-contact-flow-logs.md index c188c1e55..a135e8771 100644 --- a//connect/latest/adminguide/about-contact-flow-logs.md +++ b//connect/latest/adminguide/about-contact-flow-logs.md @@ -7 +7 @@ -# Use flow logs to track events in Amazon Connect flows +# Use flow logs to track events in Connect Customer flows @@ -9 +9 @@ -Amazon Connect flow logs provide you with real-time details about events in your flows as customers interact with them. You can also use flow logs to help debug your flows as you are creating them. If needed, you can always [roll back](./flow-version-control.html#rollback) to a previous version of a flow. +Connect Customer flow logs provide you with real-time details about events in your flows as customers interact with them. You can also use flow logs to help debug your flows as you are creating them. If needed, you can always [roll back](./flow-version-control.html#rollback) to a previous version of a flow. @@ -17 +17 @@ 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 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). +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 Connect Customer console. However, to enable logging, you also need to add a **Set logging behavior** block to your flow. For instructions, see [Enable Connect Customer flow logs in an Amazon CloudWatch log group](./contact-flow-logs.html). @@ -21 +21 @@ 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 on the Amazon Connect console: +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 Connect Customer console: @@ -25 +25 @@ These logs are saved in an S3 bucket that is created when you [select](./monitor - * **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. + * **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 Connect Customer admin website. @@ -27 +27 @@ These logs are saved in an S3 bucket that is created when you [select](./monitor - * **Enable Bot Analytics and Transcripts** in Amazon Connect on the **Flows** page. This option ensures the log includes the Amazon Lex bot transcript. + * **Enable Bot Analytics and Transcripts** in Connect Customer on the **Flows** page. This option ensures the log includes the Amazon Lex bot transcript.