AWS prescriptive-guidance documentation change
Summary
Renamed 'Amazon Connect' to 'Connect Customer' throughout the document, updated references to administrator guides and security features accordingly.
Security assessment
Changes are purely branding updates (Amazon Connect → Connect Customer) with no modifications to security guidance. Existing security content about granular permissions and IAM remains unchanged except for product naming.
Diff
diff --git a/prescriptive-guidance/latest/strategy-migration-connect/ops-considerations.md b/prescriptive-guidance/latest/strategy-migration-connect/ops-considerations.md index bc014fb0d..050f357e6 100644 --- a//prescriptive-guidance/latest/strategy-migration-connect/ops-considerations.md +++ b//prescriptive-guidance/latest/strategy-migration-connect/ops-considerations.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) @@ -20 +20 @@ The best practices in this section focus on smoothing operations and keeping end -**Desk phone alternative** – Agents can have calls delivered to a desk phone, as explained in the Amazon Connect [setup instructions](https://docs.aws.amazon.com/connect/latest/adminguide/configure-agents.html), as an alternative to a soft phone. This alternative handset must have a publicly reachable phone number, which is then configured in the agent profile. For example, this can be useful when a remote internet connection cannot support high-quality audio on the soft phone audio. In this case, the audio is sent across the traditional (PSTN) phone network. +**Desk phone alternative** – Agents can have calls delivered to a desk phone, as explained in the Connect Customer [setup instructions](https://docs.aws.amazon.com/connect/latest/adminguide/configure-agents.html), as an alternative to a soft phone. This alternative handset must have a publicly reachable phone number, which is then configured in the agent profile. For example, this can be useful when a remote internet connection cannot support high-quality audio on the soft phone audio. In this case, the audio is sent across the traditional (PSTN) phone network. @@ -37 +37 @@ The best practices in this section focus on smoothing operations and keeping end -**Billing** – AWS billing costs will increase and legacy platform costs will decrease immediately after the new contact center goes live. Contact center charges will be subsumed into AWS billing after migration. Notify your finance and accounting teams of this change so that costs from AWS accounts that host Amazon Connect instances can be mapped to the appropriate business unit. This is likely the same business unit that’s responsible for legacy platform charges. +**Billing** – AWS billing costs will increase and legacy platform costs will decrease immediately after the new contact center goes live. Contact center charges will be subsumed into AWS billing after migration. Notify your finance and accounting teams of this change so that costs from AWS accounts that host Connect Customer instances can be mapped to the appropriate business unit. This is likely the same business unit that’s responsible for legacy platform charges. @@ -39 +39 @@ The best practices in this section focus on smoothing operations and keeping end -**Access permissions** – You can provide granular permissions to your contact center users by creating [security profiles](https://docs.aws.amazon.com/connect/latest/adminguide/connect-security-profiles.html) in Amazon Connect. This feature enables you to create advanced user access models based on the principle of least privilege to perform a role. On legacy platforms, permissions are typically granted too broadly. In contrast, in Amazon Connect, you can give users access to very specific resources and activities. For example, you can grant employees permission to edit users but not create or delete them, or to view user journey contact flows but not change them. Granular permissions are a powerful way to improve user engagement and optimize how responsibilities are distributed across roles and (such as agents, operators, supervisors, and developers) and teams. In addition to using security profiles, you can use Amazon Connect with AWS Identity and Access Management (IAM) features and polices. For more information, see [How Amazon Connect works with IAM](https://docs.aws.amazon.com/connect/latest/adminguide/security_iam_service-with-iam.html) in the _Amazon Connect Administrator Guide_. +**Access permissions** – You can provide granular permissions to your contact center users by creating [security profiles](https://docs.aws.amazon.com/connect/latest/adminguide/connect-security-profiles.html) in Connect Customer. This feature enables you to create advanced user access models based on the principle of least privilege to perform a role. On legacy platforms, permissions are typically granted too broadly. In contrast, in Connect Customer, you can give users access to very specific resources and activities. For example, you can grant employees permission to edit users but not create or delete them, or to view user journey contact flows but not change them. Granular permissions are a powerful way to improve user engagement and optimize how responsibilities are distributed across roles and (such as agents, operators, supervisors, and developers) and teams. In addition to using security profiles, you can use Connect Customer with AWS Identity and Access Management (IAM) features and polices. For more information, see [How Connect Customer works with IAM](https://docs.aws.amazon.com/connect/latest/adminguide/security_iam_service-with-iam.html) in the _Connect Customer Administrator Guide_. @@ -41 +41 @@ The best practices in this section focus on smoothing operations and keeping end -**Service quotas** – Service quotas are default settings that protect you from unexpected load and consumption charges. For example, service quotas can limit you to 10 concurrent calls or 5 phone numbers per instance. We recommend that you view your service quotas and request increases to support your expected usage. For more information, see [Amazon Connect service quotas](https://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-service-limits.html) in the _Amazon Connect Administrator Guide_. +**Service quotas** – Service quotas are default settings that protect you from unexpected load and consumption charges. For example, service quotas can limit you to 10 concurrent calls or 5 phone numbers per instance. We recommend that you view your service quotas and request increases to support your expected usage. For more information, see [Connect Customer service quotas](https://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-service-limits.html) in the _Connect Customer Administrator Guide_.