- Mais recentes
- Mais votos
- Mais comentários
I will need more information about your deployment, and what exactly you have configured for the Salesforce CTI Adapter, as well as its version. In principle, if you want to invoke a Lambda from a different region or account, in the Invoke AWS Lambda function contact flow bloc, under Select a function, you can enter the ARN of a Lambda. Then set up the corresponding resource-based policy on that Lambda to allow the flow to call it. https://docs.aws.amazon.com/connect/latest/adminguide/connect-lambda-functions.html Installing the CTI Adapter using the guides setup or following the deployment guide should not give you any mismatches in regions. Since I have no additional information about why your lambda is in a different region, I am adding here some links to documentation that I hope may be clarifying some of the things you see in your deployment: https://github.com/amazon-connect/amazon-connect-salesforce-cti/blob/main/docs/lightning/02-installation/04-salesforce-lambdas-manual-setup.md
Check the CloudFormation template outputs on the region that the resources are created in. if all of them are ap-northeast-1. Then somewhere prior you either picked the wrong region or you are in the wrong region after logging into AWS Console.
You could delete the Cloudformation template for Lambda and try again. But I would carefully go through the steps again and check your region while you are in AWS console for various steps that requires it.
Like: https://amazon-connect.github.io/amazon-connect-salesforce-cti/docs/classic/installation/01-installation#setting-up-the-executeawsservice-named-credential step 8, make sure you input the right region there.
https://amazon-connect.github.io/amazon-connect-salesforce-cti/docs/classic/installation/02-guided-setup#setting-up-the-secretsmanager-secret step 2, when checking if your AWS Console is using the right region
The end result when launching the CLoudformation to create resources should be in the region you desire
Conteúdo relevante
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 3 anos
- AWS OFICIALAtualizada há 2 anos