AWS connect documentation change
Summary
Updated product branding from 'Amazon Connect' to 'Connect Customer' and maintained existing security guidance about KMS encryption
Security assessment
Changes are branding updates with no modification to security content. Existing guidance about KMS encryption requirements remains unchanged but is not new security documentation.
Diff
diff --git a/connect/latest/adminguide/agent-event-streams-enable.md b/connect/latest/adminguide/agent-event-streams-enable.md index 46c2da255..cf5be32b4 100644 --- a//connect/latest/adminguide/agent-event-streams-enable.md +++ b//connect/latest/adminguide/agent-event-streams-enable.md @@ -7 +7 @@ -# Enable agent event streams to report agent activity in Amazon Connect +# Enable agent event streams to report agent activity in Connect Customer @@ -9 +9 @@ -Agent event streams are not enabled by default. Before you can enable agent event streams in Amazon Connect, create a data stream in Amazon Kinesis Data Streams. Then, choose the Kinesis stream as the stream to use for agent event streams. Though you can use the same stream for both agent event streams and contact records, managing and getting data from the stream is much easier when you use a separate stream for each. For more information, see the [Amazon Kinesis Data Streams Developer Guide](https://docs.aws.amazon.com/streams/latest/dev/). +Agent event streams are not enabled by default. Before you can enable agent event streams in Connect Customer, create a data stream in Amazon Kinesis Data Streams. Then, choose the Kinesis stream as the stream to use for agent event streams. Though you can use the same stream for both agent event streams and contact records, managing and getting data from the stream is much easier when you use a separate stream for each. For more information, see the [Amazon Kinesis Data Streams Developer Guide](https://docs.aws.amazon.com/streams/latest/dev/). @@ -15 +15 @@ When data is sent to Kinesis, the partition key used is the agent ARN. All event -If you enable server-side encryption for the Kinesis stream you select for agent event streams, Amazon Connect cannot publish to the stream. This is because it does not have permission to Kinesis `kms:GenerateDataKey`. To work around this, first enable encryption for scheduled reports or recordings of conversations. Next, create a AWS KMS key using KMS for encryption. Finally, choose the same KMS key for your Kinesis data stream that you use for encryption of scheduled reports or recordings of conversations so that Amazon Connect has appropriate permissions to encrypt data sent to Kinesis. For more information about creating a KMS key, see [Creating Keys](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html). +If you enable server-side encryption for the Kinesis stream you select for agent event streams, Connect Customer cannot publish to the stream. This is because it does not have permission to Kinesis `kms:GenerateDataKey`. To work around this, first enable encryption for scheduled reports or recordings of conversations. Next, create a AWS KMS key using KMS for encryption. Finally, choose the same KMS key for your Kinesis data stream that you use for encryption of scheduled reports or recordings of conversations so that Connect Customer has appropriate permissions to encrypt data sent to Kinesis. For more information about creating a KMS key, see [Creating Keys](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html). @@ -19 +19 @@ If you enable server-side encryption for the Kinesis stream you select for agent - 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/). @@ -38 +38 @@ Agent event streams -Sample agent event stream in Amazon Connect +Sample agent event stream in Connect Customer