aws-sdk v3 lambda region missing even after providing region
Question
I'm migrating aws-sdk from v2 to v3 and I'm having trouble setting up the lambda client. I'm providing region during the instantiation of lambda client as shown in the docs but while running InvokeAsyncCommand on the client, I get "Region is missing" error.
The sandbox contains the issue reproduced
1 answers
solution1
0 2021-11-18 05:32:37
Adding clientConfig: {region: "region-here"} in fromCognitoIdentityPool solved the issue. I've left the code sandbox unedited for reference.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.
Related Question
Does AWS Lambda support aws-sdk v3 or not?
How to invoke a lambda function in aws-sdk v3
Nodejs modularized aws-sdk v3 size getting increased
How to call service in different region using lambda and AWS SDK
"TypeError: hashConstructor is not a constructor", error when using "@aws-sdk/signature-v4" on AWS-Lambda
does lambda layer include aws-sdk
aws-sdk for Lambda not up to date?
Can a CloudWatch Event in one region trigger a Lambda in another region of AWS?
AWS Java SDK - Unable to find a region via the region provider chain
Lambda to monitor multi region AWS changes/events
Related Tags