AWS connect documentation change
Summary
Updated terminology from 'choose-to-call/dial' to 'click-to-call/dial' and corrected blog link
Security assessment
Terminology update and link correction in security best practices document. No specific security vulnerability is addressed.
Diff
diff --git a/connect/latest/adminguide/security-bp.md b/connect/latest/adminguide/security-bp.md index fbaa6b323..418ec2523 100644 --- a//connect/latest/adminguide/security-bp.md +++ b//connect/latest/adminguide/security-bp.md @@ -181 +181 @@ Follow your security best practices for this layer with special attention to the - 3. **External** : The External layer includes contact points including chat, choose-to-call endpoints, and the PSTN for voice calls, integrations you may have with legacy contact center solutions in a Hybrid contact center architecture, and integrations you may have with other third-party solutions. Any entry point or exit point for a third party in your workload is considered the external layer. + 3. **External** : The External layer includes contact points including chat, click-to-call endpoints, and the PSTN for voice calls, integrations you may have with legacy contact center solutions in a Hybrid contact center architecture, and integrations you may have with other third-party solutions. Any entry point or exit point for a third party in your workload is considered the external layer. @@ -185 +185 @@ This layer also covers integrations customers may have with other third-party so - * You can [create contact filters for repeat and fraudulent contacts](https://aws.amazon.com/blogs/contact-center/how-to-protect-against-spam-calls-for-choose-to-dial/) using AWS Lambda to write contact details to DynamoDB from within your flow, including ANI, IP address for choose-to-dial and chat endpoints, and any other identifying information to track how many contact requests occur during a given period of time. This approach allows you to query and add contacts to deny lists, automatically disconnecting them if they exceed reasonable levels. + * You can [create contact filters for repeat and fraudulent contacts](https://aws.amazon.com/blogs/contact-center/how-to-protect-against-spam-calls-for-click-to-dial/) using AWS Lambda to write contact details to DynamoDB from within your flow, including ANI, IP address for click-to-dial and chat endpoints, and any other identifying information to track how many contact requests occur during a given period of time. This approach allows you to query and add contacts to deny lists, automatically disconnecting them if they exceed reasonable levels.