- Le plus récent
- Le plus de votes
- La plupart des commentaires
I will recommend you to read through this workshop https://catalog.workshops.aws/amazon-connect-global-resiliency/en-US
Understand the way to setup this feature initially. It does NOT take two existing instances and sync them up using the TDG. You START with only 1 instance, you then execute the API to create the replica instance that will be empty in the other region.
What the blog calls out in the prereq in step 1, is to get allow listed which the Connect SA will explain all this to you. And once allow listed, you can now deploy this blog post, which one of the step to execute the replica API to create the replica instance, you will now have your 2 instances that will have the same instance ID but different region name in the full ARN to continue the rest of the blog on having a sample UI to manage the TDG
- Correct the guide assumes you will be creating two new instances.
- Not sure I understand your question, the Stack needs to run to completion in order to provide what the blog shows.
Now, a personal opinion about Connect global resiliency. It’s a good start, but not great yet. You can do something very similar if you keep ownership of your phone numbers. It will be more work, but in my opinion the cost benefits are there. Until the you’re able to replicate Connect configuration across instances automatically this approach is only useful for very specific use cases.
David
Hi,
This post will bring you interesting guidance on your questions: https://aws.amazon.com/blogs/contact-center/build-a-multi-region-resilient-contact-center-with-amazon-connect-global-resiliency/
In particular, the CloudFormation-based approach (See template at https://github.com/aws-samples/ac-multi-region-apis/blob/main/template.yaml) is very powerful to clone very efficiently your initial infratructure (or part of it) to conduct the tests that you want with no risk on production infra.
Best
Didier
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a un an
- demandé il y a 5 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 2 ans
Thank you, that workshop is exactly what I needed.