Source note · Troubleshooting Amazon Connect flows
To call a Lambda function in another Region or account, enter its ARN in the block and add a resource-based policy on the function with principal connect.amazonaws.com, source account set to the instance's account and source ARN set to the instance ARN.
Checked 2026-10-02
- Vendor
- Amazon Web Services
- Product
- Amazon Connect
- Subsystem
- Lambda integration
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- Grant Connect Customer access to your AWS Lambda functions — Amazon Web Services · tier 2 current vendor documentation · Add a Lambda function to your Connect Customer instance, step 4 Tip
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting Amazon Connect flows: source note amazon-connect-flow-troubleshooting-lambda-cross-region-perm. WarmTransfer. https://warmtransfer.net/knowledge/claims/amazon-connect-flow-troubleshooting-lambda-cross-region-perm
BibTeX
@misc{warmtransfer-claim-amazon-connect-flow-troubleshooting-lambda-cross-region-perm,
title = {Troubleshooting Amazon Connect flows: source note amazon-connect-flow-troubleshooting-lambda-cross-region-perm},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/amazon-connect-flow-troubleshooting-lambda-cross-region-perm},
note = {Source note amazon-connect-flow-troubleshooting-lambda-cross-region-perm, checked 2026-10-02}
}