Amazon Connect Global Resiliency requirements

If you have decided that Amazon Connect Global Resiliency is the appropriate deployment for you, ensure you adhere to the following pre-requisites before onboarding:

• Port all phone numbers you want to enable to be multi-region to Amazon Connect.

• You must have an existing production SAML 2.0-enabled Amazon Connect instance in a Region where Amazon Connect Global Resiliency is available. To confirm, see Global Resiliency availability by Region.

• It is recommended to onboard and test Amazon Connect Global Resiliency services in a test environment before onboarding production traffic.

• Request that ALL service quotas in the replica instance match the service quotas in the source instance: Create a service quota increase case in the AWS Management Console > Support.

• Ensure your Lambda functions across AWS Regions have the same name.

• Update your flows to replace any hardcoded Regions with a $.AwsRegion or $['AwsRegion'] parameter.

• For Amazon Lex bots, you can do one of the following:

  • Use Amazon Lex Global Resiliency to replicate bots across AWS Regions and retain the bot ID.

  • Change your flows to branch based on the AWS Region where the flow is running. At flow runtime, these parameters are replaced with the Region where the flow is run, as shown in the following example.