I'm a newbie in NodeJS and I'm not really familiar with all this thing of "npm". I mean, I didn't expect that just for one "npm install" I will get 10Mb of 30 different folders.  After a bunch of minutes when I processed this fact, I just realize that there are a lot of junk in those folders. They are not "compiled", let's call it this way... There are "readme" files, source files, test scripts, example applications, docs and so on!!! Many of modules has duplications of another modules inside their folders. Like “inherits”, “core-util-is”, “tedious” etc. Modules inside modules, Karl! And inside them – another modules, that already exist in other modules in the project. Whaaaaat???!!! There is an example of one of them - I'm in "node_modules" and in "bl" folder, but there is another "node_modules" folder inside it as well as "test", "readme" and all this junk here. And all of ...

This thing is not trivial and I didn't found any simple explanation about this. So that is  select an existing resource (eg. "users") click on "Actions" dropdown and select "Create Resource" in " Resource Name " put parameter name in curly braces (eg. {userid}) in " Resource Path " you should see read-only text " /users/ " and textbox for parameter write {userid} in this textbox and click " Create Resource " you should see a new branch in your API tree - /{userid} . Select it. click  "Create Resource"-"Create Method" and add ANY method there integrate it with Lambda function you alrteady used for ANY of this resource (don't forget check " Use Lambda Proxy integration ") select this new brand ANY method, go to "Method Request" and ensure that there is "userid" parameter in "Request Paths" section That is it. Now you should handle it in your Lambda (to...