AWS connect documentation change
Summary
Added hyperlinks to detailed documentation for logging Amazon Connect flows to CloudWatch and setting up alerts
Security assessment
The change enhances existing security best practices documentation by linking to implementation guides, but does not address a specific security vulnerability or incident.
Diff
diff --git a/connect/latest/adminguide/security-best-practices.md b/connect/latest/adminguide/security-best-practices.md index c80cfdb07..ccc376a84 100644 --- a//connect/latest/adminguide/security-best-practices.md +++ b//connect/latest/adminguide/security-best-practices.md @@ -76 +76 @@ Following is an example SCP that can be applied at the AWS Account, Organization -Logging and monitoring are important for the availability, reliability and, performance of contact center. You should log relevant information from Amazon Connect flows to CloudWatch and build alerts and notifications based on the same. +Logging and monitoring are important for the availability, reliability and, performance of contact center. You should [log relevant information from Amazon Connect flows to CloudWatch](./contact-flow-logs.html) and [build alerts and notifications](./contact-flow-log-alerts.html) based on the same. @@ -78 +78 @@ Logging and monitoring are important for the availability, reliability and, perf -Define log retention requirements and lifecycle policies early on, and plan to move log files to cost-efficient storage locations as soon as practical. Amazon Connect public APIs log to CloudTrail. Review and automate actions based on CloudTrail logs. +Define log retention requirements and lifecycle policies early on, and plan to move log files to cost-efficient storage locations as soon as practical. Amazon Connect public APIs log to CloudTrail; for more information, see [Log Amazon Connect API calls with AWS CloudTrail](./logging-using-cloudtrail.html). Review and automate actions based on CloudTrail logs.