# AWS lambda problems **URL:** \ **Category:** Questions\ **Created:** [November 21, 2020, 12:56pm UTC](https://community.n8n.io/t/aws-lambda-problems/3118 "2020-11-21T12:56:56Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![liushengyi](https://avatars.discourse-cdn.com/v4/letter/l/eb8c5e/32.png) [@liushengyi](https://community.n8n.io/u/liushengyi)\ **Post date:** [November 21, 2020, 12:56pm UTC](https://community.n8n.io/t/aws-lambda-problems/3118/1 "2020-11-21T12:56:56Z")
I want to use the node for AWS lambda to execute my task.but i meet a problems. ![image](https://europe1.discourse-cdn.com/n8n/original/2X/3/34a6705a218a619350938058bdecd83c94916d92.png) how should I solve it ? ---
**Author:** ![RicardoE105](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ricardoe105/32/550_2.png) [@RicardoE105](https://community.n8n.io/u/RicardoE105)\ **Post date:** [November 21, 2020, 1:56pm UTC](https://community.n8n.io/t/aws-lambda-problems/3118/2 "2020-11-21T13:56:18Z")
Welcome to the community. Just tested it and it’s working just fine for me. Why is it the function field in red? is it the server running? in which line the body is undefined? ---
**Author:** ![liushengyi](https://avatars.discourse-cdn.com/v4/letter/l/eb8c5e/32.png) [@liushengyi](https://community.n8n.io/u/liushengyi)\ **Post date:** [November 21, 2020, 4:08pm UTC](https://community.n8n.io/t/aws-lambda-problems/3118/3 "2020-11-21T16:08:55Z")
Thanks for reply, my aws region is cn-northwest-1 . Could that be the reason？ ![image](https://europe1.discourse-cdn.com/n8n/original/2X/6/6ec85b52cb4497027d13688ead4ee9791aa2a9ae.png) After I chose the Credentials，the function field change to red. It doesn’t change whether I fill in the function name or not。 ![image](https://europe1.discourse-cdn.com/n8n/original/2X/d/db71d43afbefd9fdc32f759c3ecc01761f975563.png) ---
**Author:** ![RicardoE105](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ricardoe105/32/550_2.png) [@RicardoE105](https://community.n8n.io/u/RicardoE105)\ **Post date:** [November 21, 2020, 4:27pm UTC](https://community.n8n.io/t/aws-lambda-problems/3118/4 "2020-11-21T16:27:29Z")
There is no region called _cn-northwest-1_ according to this > **[Regions and Zones - Amazon Elastic Compute Cloud](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-regions)** > > Describes the Regions, Availability Zones, Local Zones, Outposts, and Wavelength Zones world-wide where you can host your instances. ---
**Author:** ![liushengyi](https://avatars.discourse-cdn.com/v4/letter/l/eb8c5e/32.png) [@liushengyi](https://community.n8n.io/u/liushengyi)\ **Post date:** [November 21, 2020, 5:11pm UTC](https://community.n8n.io/t/aws-lambda-problems/3118/5 "2020-11-21T17:11:13Z")
> [@RicardoE105](#): > > There is no region called _cn-northwest-1_ according to this It may just be that the document isn’t updated, but it’s real ![image](https://europe1.discourse-cdn.com/n8n/original/2X/c/c1fc25b209b0128759ae082822090772b0e07246.png) ---
**Author:** ![RicardoE105](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ricardoe105/32/550_2.png) [@RicardoE105](https://community.n8n.io/u/RicardoE105)\ **Post date:** [November 21, 2020, 11:45pm UTC](https://community.n8n.io/t/aws-lambda-problems/3118/6 "2020-11-21T23:45:04Z")
Got it. Well I will suggest you make sure the credentials have attached a policy with access to execute a lambda function. ---
**Author:** ![liushengyi](https://avatars.discourse-cdn.com/v4/letter/l/eb8c5e/32.png) [@liushengyi](https://community.n8n.io/u/liushengyi)\ **Post date:** [November 23, 2020, 2:16am UTC](https://community.n8n.io/t/aws-lambda-problems/3118/7 "2020-11-23T02:16:04Z")
I confirmed it again.the credentials have attached a policy with access to execute a lambda function.Is there any other plan ？ ---
**Author:** ![liushengyi](https://avatars.discourse-cdn.com/v4/letter/l/eb8c5e/32.png) [@liushengyi](https://community.n8n.io/u/liushengyi)\ **Post date:** [November 23, 2020, 8:43am UTC](https://community.n8n.io/t/aws-lambda-problems/3118/8 "2020-11-23T08:43:22Z")
Thanks for reply. I finally solved this problem, the core problem is the correct endpoint is [lambda.cn-northwest-1.amazonaws.com.cn](http://lambda.cn-northwest-1.amazonaws.com.cn) ,but the source code is `${service}.${credentials.region}.amazonaws.com` ---
**Author:** ![RicardoE105](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ricardoe105/32/550_2.png) [@RicardoE105](https://community.n8n.io/u/RicardoE105)\ **Post date:** [November 23, 2020, 2:04pm UTC](https://community.n8n.io/t/aws-lambda-problems/3118/9 "2020-11-23T14:04:30Z")
ahh that is quite weird as it works for me with the current form. I wonder if this applies just for that region. ---
**Author:** ![liushengyi](https://avatars.discourse-cdn.com/v4/letter/l/eb8c5e/32.png) [@liushengyi](https://community.n8n.io/u/liushengyi)\ **Post date:** [November 29, 2020, 6:43am UTC](https://community.n8n.io/t/aws-lambda-problems/3118/10 "2020-11-29T06:43:54Z")
@jan the lambda endpoint url for _cn-northwest-1_ and _cn-north-1_ is endswith [amazonaws.com.cn](http://amazonaws.com.cn) ，Can this compatible support be updated to the next release ? ---
**Author:** ![RicardoE105](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ricardoe105/32/550_2.png) [@RicardoE105](https://community.n8n.io/u/RicardoE105)\ **Post date:** [November 29, 2020, 2:56pm UTC](https://community.n8n.io/t/aws-lambda-problems/3118/11 "2020-11-29T14:56:22Z")
Added it to my TODO list. ---
**Author:** ![liushengyi](https://avatars.discourse-cdn.com/v4/letter/l/eb8c5e/32.png) [@liushengyi](https://community.n8n.io/u/liushengyi)\ **Post date:** [January 11, 2021, 12:30pm UTC](https://community.n8n.io/t/aws-lambda-problems/3118/12 "2021-01-11T12:30:34Z")
@RicardoE105 I was pleasantly surprised to find that the latest version of N8N already supports custom endpoints. I couldn’t wait to use it, but I got the following error. ![image](https://europe1.discourse-cdn.com/n8n/original/2X/3/38c5eb7d28d1626376c1774937a0ea7cbefb44f8.png) I don’t know what the problem is. The Endpoint still works when I manually modify the source code in the last version ---
**Author:** ![krynble](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/krynble/32/2010_2.png) [@krynble](https://community.n8n.io/u/krynble)\ **Post date:** [February 5, 2021, 10:51am UTC](https://community.n8n.io/t/aws-lambda-problems/3118/13 "2021-02-05T10:51:14Z")
Hey @liushengyi about two weeks ago I fixed a bug with this issue here: [Fix AWS lambda and SNS problem with signature by krynble · Pull Request #1361 · n8n-io/n8n · GitHub](https://github.com/n8n-io/n8n/pull/1361) Should be working fine now. Have you tried it recently? I think it was fixed in version 0.101 if I am not mistaken. ---
**Author:** ![liushengyi](https://avatars.discourse-cdn.com/v4/letter/l/eb8c5e/32.png) [@liushengyi](https://community.n8n.io/u/liushengyi)\ **Post date:** [February 7, 2021, 2:20am UTC](https://community.n8n.io/t/aws-lambda-problems/3118/14 "2021-02-07T02:20:57Z")
It has been working,Thank you~