AWS connect documentation change
Summary
Replaced all instances of 'Amazon Connect' with 'Connect Customer'. Updated document title and section references. No changes to logging/monitoring functionality or security practices.
Security assessment
Changes are limited to service name rebranding without alterations to security-relevant content about logging, monitoring, CloudWatch, or CloudTrail. The security implications of monitoring practices remain identical despite terminology changes.
Diff
diff --git a/connect/latest/adminguide/logging-and-monitoring.md b/connect/latest/adminguide/logging-and-monitoring.md index 3d6f5d82c..cb5d09127 100644 --- a//connect/latest/adminguide/logging-and-monitoring.md +++ b//connect/latest/adminguide/logging-and-monitoring.md @@ -7 +7 @@ -# Logging and monitoring Amazon Connect +# Logging and monitoring Connect Customer @@ -11 +11 @@ Monitoring is important for maintaining the reliability, availability, and perfo -You should collect monitoring data from all of the parts of your AWS solution so that you can more easily debug a multipoint failure if one occurs. But before you start monitoring Amazon Connect, you should create a monitoring plan that includes answers to the following questions: +You should collect monitoring data from all of the parts of your AWS solution so that you can more easily debug a multipoint failure if one occurs. But before you start monitoring Connect Customer, you should create a monitoring plan that includes answers to the following questions: @@ -15 +15 @@ You should collect monitoring data from all of the parts of your AWS solution so - * What data about your Amazon Connect instance will you monitor? + * What data about your Connect Customer instance will you monitor? @@ -28 +28 @@ You should collect monitoring data from all of the parts of your AWS solution so -See the following topics to learn how to use Amazon CloudWatch Logs and AWS CloudTrail to monitor Amazon Connect and describes the Amazon Connect metrics sent to CloudWatch: +See the following topics to learn how to use Amazon CloudWatch Logs and AWS CloudTrail to monitor Connect Customer and describes the Connect Customer metrics sent to CloudWatch: @@ -30 +30 @@ See the following topics to learn how to use Amazon CloudWatch Logs and AWS Clou - * [Monitoring your Amazon Connect instance using CloudWatch](./monitoring-cloudwatch.html) + * [Monitoring your Connect Customer instance using CloudWatch](./monitoring-cloudwatch.html) @@ -32 +32 @@ See the following topics to learn how to use Amazon CloudWatch Logs and AWS Clou - * [Log Amazon Connect API calls with AWS CloudTrail](./logging-using-cloudtrail.html) + * [Log Connect Customer API calls with AWS CloudTrail](./logging-using-cloudtrail.html) @@ -43 +43 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Using service-linked roles for Amazon Connect Managed Synchronization +Using service-linked roles for Connect Customer Managed Synchronization