AWS prescriptive-guidance documentation change
Summary
Renamed 'Amazon Connect' to 'Connect Customer' in navigation breadcrumb and design documentation section
Security assessment
The changes are purely branding/naming updates without modifying security content. The security section reference remains unchanged.
Diff
diff --git a/prescriptive-guidance/latest/strategy-migration-connect/tech-foundation.md b/prescriptive-guidance/latest/strategy-migration-connect/tech-foundation.md index 86a749488..b90c1024e 100644 --- a//prescriptive-guidance/latest/strategy-migration-connect/tech-foundation.md +++ b//prescriptive-guidance/latest/strategy-migration-connect/tech-foundation.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Strategies for migrating your contact center to Amazon Connect](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Strategies for migrating your contact center to Connect Customer](welcome.html) @@ -43 +43 @@ Workshop attendees: -In this phase, you produce design documents. You might have your own conventions or processes for creating design artifacts. We recommend including at least three sections in the design document: Amazon Connect configuration, networking, and security. Each section will likely have different, specialized stakeholder groups to ensure effective reviews and sign-offs, so it might be more practical to create separate documents for these three areas. Stakeholders should include architects, the security and compliance team, and platform owners. +In this phase, you produce design documents. You might have your own conventions or processes for creating design artifacts. We recommend including at least three sections in the design document: Connect Customer configuration, networking, and security. Each section will likely have different, specialized stakeholder groups to ensure effective reviews and sign-offs, so it might be more practical to create separate documents for these three areas. Stakeholders should include architects, the security and compliance team, and platform owners.