AWS connect documentation change
Summary
Updated documentation to replace 'Amazon Connect' with 'Connect Customer' throughout the document, including service names, instance references, and SAML terminology.
Security assessment
The changes are purely branding/naming updates from 'Amazon Connect' to 'Connect Customer'. No security vulnerabilities, configurations, or features were modified or added. The SAML authentication workflow remains functionally identical.
Diff
diff --git a/connect/latest/adminguide/integrate-idp.md b/connect/latest/adminguide/integrate-idp.md index 8af19b660..ec45dd0c7 100644 --- a//connect/latest/adminguide/integrate-idp.md +++ b//connect/latest/adminguide/integrate-idp.md @@ -9 +9 @@ Before you beginImportant things to knowHow to integrate your identity provider -# Integrate your identity provider (IdP) with an Amazon Connect Global Resiliency SAML sign in endpoint +# Integrate your identity provider (IdP) with an Connect Customer Global Resiliency SAML sign in endpoint @@ -15 +15 @@ To enable your agents to sign in once and be logged into both AWS Regions to pro -You must enable SAML for your Amazon Connect instance to use Amazon Connect Global Resiliency. For information about getting started with IAM federation, see [Enabling SAML 2.0 federated users to access the AWS Management Console](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-saml.html). +You must enable SAML for your Connect Customer instance to use Connect Customer Global Resiliency. For information about getting started with IAM federation, see [Enabling SAML 2.0 federated users to access the AWS Management Console](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-saml.html). @@ -21 +21 @@ You must enable SAML for your Amazon Connect instance to use Amazon Connect Glob - * To perform the steps in this topic, you'll need your instance ID. For instructions about how to find it, see [Find your Amazon Connect instance ID or ARN](./find-instance-arn.html). + * To perform the steps in this topic, you'll need your instance ID. For instructions about how to find it, see [Find your Connect Customer instance ID or ARN](./find-instance-arn.html). @@ -23 +23 @@ You must enable SAML for your Amazon Connect instance to use Amazon Connect Glob - * You will also need to know the source Region of your Amazon Connect instances. For instructions about how to find it, see [How to find the source Region of your Amazon Connect instances](./create-replica-connect-instance.html#how-to-find-source-region-of-instances). + * You will also need to know the source Region of your Connect Customer instances. For instructions about how to find it, see [How to find the source Region of your Connect Customer instances](./create-replica-connect-instance.html#how-to-find-source-region-of-instances). @@ -27 +27 @@ You must enable SAML for your Amazon Connect instance to use Amazon Connect Glob -To configure Approved Origins at the instance level, follow the steps in [Use an allowlist for integrated applications in Amazon Connect](./app-integration.html). +To configure Approved Origins at the instance level, follow the steps in [Use an allowlist for integrated applications in Connect Customer](./app-integration.html). @@ -29 +29 @@ To configure Approved Origins at the instance level, follow the steps in [Use an - * Agents must be created already in _both_ your source and replica Amazon Connect instances and have the same username as the role session name from your identity provider (IdP). Otherwise, you will receive a `UserNotOnboardedException` exception and risk losing agent redundancy capabilities between your instances. + * Agents must be created already in _both_ your source and replica Connect Customer instances and have the same username as the role session name from your identity provider (IdP). Otherwise, you will receive a `UserNotOnboardedException` exception and risk losing agent redundancy capabilities between your instances. @@ -31 +31 @@ To configure Approved Origins at the instance level, follow the steps in [Use an - * You must associate agents to a traffic distribution group before agents attempt to sign in. Otherwise agent sign-in will fail with a `ResourceNotFoundException`. For information about how to setup your traffic distribution groups and associate agents to them, see [Associate agents to Amazon Connect instances across multiple AWS Regions](./associate-agents-across-regions.html). + * You must associate agents to a traffic distribution group before agents attempt to sign in. Otherwise agent sign-in will fail with a `ResourceNotFoundException`. For information about how to setup your traffic distribution groups and associate agents to them, see [Associate agents to Connect Customer instances across multiple AWS Regions](./associate-agents-across-regions.html). @@ -33 +33 @@ To configure Approved Origins at the instance level, follow the steps in [Use an - * When your agents federate into Amazon Connect with the new SAML sign-in URL, Amazon Connect Global Resiliency always attempts to log the agent into both your source and replica Regions / instances, no matter how `SignInConfig` is configured in your traffic distribution group. You can verify this by checking CloudTrail logs. + * When your agents federate into Connect Customer with the new SAML sign-in URL, Connect Customer Global Resiliency always attempts to log the agent into both your source and replica Regions / instances, no matter how `SignInConfig` is configured in your traffic distribution group. You can verify this by checking CloudTrail logs. @@ -35 +35 @@ To configure Approved Origins at the instance level, follow the steps in [Use an - * The `SignInConfig` distribution in your default traffic distribution group only determines which AWS Region is used to facilitate sign-in. Regardless of how your `SignInConfig` distribution is configured, Amazon Connect always attempts to sign in agents to both Regions of your Amazon Connect instance. + * The `SignInConfig` distribution in your default traffic distribution group only determines which AWS Region is used to facilitate sign-in. Regardless of how your `SignInConfig` distribution is configured, Connect Customer always attempts to sign in agents to both Regions of your Connect Customer instance. @@ -37 +37 @@ To configure Approved Origins at the instance level, follow the steps in [Use an - * After replicating an Amazon Connect instance, only one SAML sign-in endpoint is generated for your instances. This endpoint always contains the source AWS Region in the URL. + * After replicating an Connect Customer instance, only one SAML sign-in endpoint is generated for your instances. This endpoint always contains the source AWS Region in the URL. @@ -39 +39 @@ To configure Approved Origins at the instance level, follow the steps in [Use an - * You don't need to configure a relay state when using the personalized SAML sign-in URL with Amazon Connect Global Resiliency. + * You don't need to configure a relay state when using the personalized SAML sign-in URL with Connect Customer Global Resiliency. @@ -46 +46 @@ To configure Approved Origins at the instance level, follow the steps in [Use an - 1. When you create a replica of your Amazon Connect instance using the [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIReference/API_ReplicateInstance.html) API, a personalized SAML sign-in URL is generated for your Amazon Connect instances. The URL is generated in the following format: + 1. When you create a replica of your Connect Customer instance using the [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIReference/API_ReplicateInstance.html) API, a personalized SAML sign-in URL is generated for your Connect Customer instances. The URL is generated in the following format: @@ -127 +127 @@ https://aws.amazon.com/SAML/Attributes/Role | `saml-role-arn`,`identity-provide - * `instanceId`: The identifier of your Amazon Connect instance. For instructions about how to find your instance ID, see [Find your Amazon Connect instance ID or ARN](./find-instance-arn.html). + * `instanceId`: The identifier of your Connect Customer instance. For instructions about how to find your instance ID, see [Find your Connect Customer instance ID or ARN](./find-instance-arn.html). @@ -129 +129 @@ https://aws.amazon.com/SAML/Attributes/Role | `saml-role-arn`,`identity-provide - * `accountId`: The AWS account ID where the Amazon Connect instances are located. + * `accountId`: The AWS account ID where the Connect Customer instances are located. @@ -131 +131 @@ https://aws.amazon.com/SAML/Attributes/Role | `saml-role-arn`,`identity-provide - * `role`: Set to the name or Amazon Resource Name (ARN) of the SAML role used for Amazon Connect federation. + * `role`: Set to the name or Amazon Resource Name (ARN) of the SAML role used for Connect Customer federation.