AWS connect documentation change
Summary
Rebranded all references from 'Amazon Connect' to 'Connect Customer' including the title, section headers, and recommendation text. Updated terminology for the global resiliency feature.
Security assessment
The changes are purely branding/naming updates with no security implications. No vulnerabilities, security features, or security configurations were modified or documented.
Diff
diff --git a/connect/latest/adminguide/single-instance-multiple-instances.md b/connect/latest/adminguide/single-instance-multiple-instances.md index 09ac9f79b..7dd8ca53f 100644 --- a//connect/latest/adminguide/single-instance-multiple-instances.md +++ b//connect/latest/adminguide/single-instance-multiple-instances.md @@ -9 +9 @@ Single instanceMultiple instancesSummary -# Amazon Connect: Single Instance or Multiple Instances? +# Connect Customer: Single Instance or Multiple Instances? @@ -11 +11 @@ Single instanceMultiple instancesSummary -## Single instance of Amazon Connect (including single ACGR pair) +## Single instance of Connect Customer (including single ACGR pair) @@ -39 +39 @@ A centralized contact center operation with shared infrastructure and unified cu -## Multiple instances of Amazon Connect +## Multiple instances of Connect Customer @@ -75 +75 @@ Enterprises with geographic, regulatory, or security requirements infeasible to -The decision of single- vs. multiple-instance architecture is nuanced, and highly dependent on the nature of the customer's requirements. Considering the scalability, customizability, programmability, and security of Amazon Connect, we generally recommend single-instance Amazon Connect architectures (including a single Amazon Connect Global Resiliency pair) in the absence of compelling requirements requiring multiple regions. +The decision of single- vs. multiple-instance architecture is nuanced, and highly dependent on the nature of the customer's requirements. Considering the scalability, customizability, programmability, and security of Connect Customer, we generally recommend single-instance Connect Customer architectures (including a single Connect Customer Global Resiliency pair) in the absence of compelling requirements requiring multiple regions.