AWS connect documentation change
Summary
Updated terminology (facilitate→help, click-to-call→choose-to-call) and blog link reference
Security assessment
Terminology changes don't alter security guidance. Blog link update maintains existing anti-fraud content but doesn't introduce new security documentation.
Diff
diff --git a/connect/latest/adminguide/security-bp.md b/connect/latest/adminguide/security-bp.md index a7263cd1b..fbaa6b323 100644 --- a//connect/latest/adminguide/security-bp.md +++ b//connect/latest/adminguide/security-bp.md @@ -163 +163 @@ Connect Customer security can be divided into three logical layers as illustrate - 1. **Agent workstation**. The agent workstation layer is not managed by AWS and consists of any physical equipment and third-party technologies, services, and endpoints that facilitate your agent’s voice, data, and access the Connect Customer interface layer. + 1. **Agent workstation**. The agent workstation layer is not managed by AWS and consists of any physical equipment and third-party technologies, services, and endpoints that help your agent’s voice, data, and access the Connect Customer interface layer. @@ -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, 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. + 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. @@ -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-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. + * 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.