AWS connect documentation change
Summary
Updated terminology from 'Amazon Connect' to 'Connect Customer' throughout the document, including product names, workshop references, and console paths. Changed 'ACGR' to 'Connect Customer Global Resiliency'.
Security assessment
The changes are purely branding/naming updates without any security content modifications. The IAM permissions reference remains unchanged except for terminology. No vulnerabilities, security fixes, or new security features are introduced.
Diff
diff --git a/connect/latest/adminguide/create-replica-connect-instance.md b/connect/latest/adminguide/create-replica-connect-instance.md index 54e3af964..8d43efe20 100644 --- a//connect/latest/adminguide/create-replica-connect-instance.md +++ b//connect/latest/adminguide/create-replica-connect-instance.md @@ -9 +9 @@ Important things to knowCharacteristics of the replica instanceWhat resources ar -# Create a replica of your existing Amazon Connect instance +# Create a replica of your existing Connect Customer instance @@ -13 +13 @@ Important things to knowCharacteristics of the replica instanceWhat resources ar -**New user?** Check out the [Amazon Connect Global Resiliency Workshop](https://catalog.workshops.aws/amazon-connect-global-resiliency/en-US). This online course guides you through the process of onboarding and testing phone number and agent failover using new APIs through the AWS CLI. +**New user?** Check out the [Connect Customer Global Resiliency Workshop](https://catalog.workshops.aws/amazon-connect-global-resiliency/en-US). This online course guides you through the process of onboarding and testing phone number and agent failover using new APIs through the AWS CLI. @@ -15 +15 @@ Important things to knowCharacteristics of the replica instanceWhat resources ar -Global Resiliency is available only for Amazon Connect instances created in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Osaka), Asia Pacific (Tokyo), Europe (Frankfurt), and Europe (London). +Global Resiliency is available only for Connect Customer instances created in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Osaka), Asia Pacific (Tokyo), Europe (Frankfurt), and Europe (London). @@ -26 +26 @@ Global Resiliency is available only for Amazon Connect instances created in the -To obtain access to this feature, contact your Amazon Connect Solutions Architect or Technical Account Manager. +To obtain access to this feature, contact your Connect Customer Solutions Architect or Technical Account Manager. @@ -28 +28 @@ To obtain access to this feature, contact your Amazon Connect Solutions Architec -You call the [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIReference/API_ReplicateInstance.html) API to create a replica of your Amazon Connect instance in another AWS Region and to copy configuration information for Amazon Connect resources across AWS Regions. +You call the [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIReference/API_ReplicateInstance.html) API to create a replica of your Connect Customer instance in another AWS Region and to copy configuration information for Connect Customer resources across AWS Regions. @@ -53 +53 @@ You call the [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIR - * Make sure you have the minimum required IAM permissions to create an instance. See [Required permissions for using custom IAM policies to manage access to the Amazon Connect console](./security-iam-amazon-connect-permissions.html). + * Make sure you have the minimum required IAM permissions to create an instance. See [Required permissions for using custom IAM policies to manage access to the Connect Customer console](./security-iam-amazon-connect-permissions.html). @@ -67 +67 @@ You call the [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIR - * To allow AWS managed keys in the replica instance, using the AWS console, create a temporary Amazon Connect instance in the Region where you are planning to create the replica instance. This will create the default AWS managed keys for Amazon Connect. + * To allow AWS managed keys in the replica instance, using the AWS console, create a temporary Connect Customer instance in the Region where you are planning to create the replica instance. This will create the default AWS managed keys for Connect Customer. @@ -69 +69 @@ You call the [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIR - * [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIReference/API_ReplicateInstance.html) copies the Amazon Connect configuration across AWS Regions as part of the initial replication process. After this first step completes, any changes made to either the original or mirrored resources at a later time are continuously synchronized. This happens bidirectionally, from source to replica, and from the replica to the source. + * [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIReference/API_ReplicateInstance.html) copies the Connect Customer configuration across AWS Regions as part of the initial replication process. After this first step completes, any changes made to either the original or mirrored resources at a later time are continuously synchronized. This happens bidirectionally, from source to replica, and from the replica to the source. @@ -73 +73 @@ You call the [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIR - * For instances in Asia Pacific (Tokyo), only phone numbers that are explicitly enabled for Amazon Connect Global Resiliency (ACGR) will support complete replication behavior to Asia Pacific (Osaka). When routing through Asia Pacific (Osaka), inbound calls may experience delivery times of up to 20 seconds. + * For instances in Asia Pacific (Tokyo), only phone numbers that are explicitly enabled for Connect Customer Global Resiliency (ACGR) will support complete replication behavior to Asia Pacific (Osaka). When routing through Asia Pacific (Osaka), inbound calls may experience delivery times of up to 20 seconds. @@ -77 +77 @@ You call the [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIR - * As the configuration is propagated across AWS Regions, you can view the progress in AWS CloudTrail logs. Or, in the Amazon Connect admin website you can navigate to **User management** , **View historical changes** to view an audit trail of changes to the users. Audit trails are also available for other configurations. + * As the configuration is propagated across AWS Regions, you can view the progress in AWS CloudTrail logs. Or, in the Connect Customer admin website you can navigate to **User management** , **View historical changes** to view an audit trail of changes to the users. Audit trails are also available for other configurations. @@ -96 +96 @@ In the case of resource name conflicts, [ReplicateInstance](https://docs.aws.ama - * The replica Amazon Connect instance is created in the same AWS account as your existing Amazon Connect instance. + * The replica Connect Customer instance is created in the same AWS account as your existing Connect Customer instance. @@ -110 +110 @@ Use the [CreateTrafficDistributionGroup](https://docs.aws.amazon.com/connect/lat - * You use `SignInConfig` to choose the backend sign-in servers to facilitate the agent signing in to their Amazon Connect instance. For example, if you call `UpdateTrafficDistribution` with a modified `SignInConfig` and a non-default `TrafficDistributionGroup`, an `InvalidRequestException` is returned. + * You use `SignInConfig` to choose the backend sign-in servers to facilitate the agent signing in to their Connect Customer instance. For example, if you call `UpdateTrafficDistribution` with a modified `SignInConfig` and a non-default `TrafficDistributionGroup`, an `InvalidRequestException` is returned. @@ -112 +112 @@ Use the [CreateTrafficDistributionGroup](https://docs.aws.amazon.com/connect/lat - * The replica instance has the same instance ID as the Amazon Connect instance it is replicated from. + * The replica instance has the same instance ID as the Connect Customer instance it is replicated from. @@ -119 +119 @@ Use the [CreateTrafficDistributionGroup](https://docs.aws.amazon.com/connect/lat -[ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIReference/API_ReplicateInstance.html) mirrors the following Amazon Connect resources across AWS Regions. +[ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIReference/API_ReplicateInstance.html) mirrors the following Connect Customer resources across AWS Regions. @@ -206 +206 @@ The service quotas for these resources are automatically matched across AWS Regi -After initial replication, configuration changes are replicated bidirectionally between replicated instances in near real-time. If this fails, Amazon Connect Global Resiliency attempts to sync updates within 30 minutes. +After initial replication, configuration changes are replicated bidirectionally between replicated instances in near real-time. If this fails, Connect Customer Global Resiliency attempts to sync updates within 30 minutes. @@ -210 +210 @@ After initial replication, configuration changes are replicated bidirectionally -After your replica Amazon Connect instance is created, you need to configure it: +After your replica Connect Customer instance is created, you need to configure it: @@ -227 +227 @@ Contact AWS Support for help with the following activities: - * To understand mirroring status beyond what's available in the CloudTrail logs and audit trail in the Amazon Connect admin website. + * To understand mirroring status beyond what's available in the CloudTrail logs and audit trail in the Connect Customer admin website. @@ -251 +251 @@ A [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIReference/AP -## How to find the source Region of your Amazon Connect instances +## How to find the source Region of your Connect Customer instances @@ -253 +253 @@ A [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIReference/AP -If you forget which Region is your source Region for your Amazon Connect instances, perform the following steps to find it: +If you forget which Region is your source Region for your Connect Customer instances, perform the following steps to find it: @@ -257 +257 @@ If you forget which Region is your source Region for your Amazon Connect instanc - 2. For any traffic distribution group in the response list, the returned `InstanceARN` includes the source Region. For example in the following ARN, `source-region` would be the Region of your Amazon Connect instance. + 2. For any traffic distribution group in the response list, the returned `InstanceARN` includes the source Region. For example in the following ARN, `source-region` would be the Region of your Connect Customer instance.