Hi everyone,
I’m currently using AWS SAM CLI with NodeJS and was surprised to find that the requests were significantly slower when run locally. Luckily, I came across a post that suggested adding –skip-pull-image to your start-api command:
sam local start-api --skip-pull-image
This brought my requests down to under a second. Thanks to the following link for the info: https://github.com/awslabs/aws-sam-cli/issues/134#issuecomment-406786704
Hi everyone,
This will just be a living cheat sheet or quick reference for using AWS SAM with nodejs. I’ll add to it as I find things that are useful or I might need again.
General AWS SAM Info:
| Description | Example | More |
|---|---|---|
| Validate template | sam validate | |
| Start AWS Sam Locally | https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-quick-start.html | |
| Access config variable in Lambda | const CAT_BREED_TABLE = process.env.CAT_BREED_TABLE; | https://stackoverflow.com/a/48491845/522859 |
| Dynamically reference another resource in template.yml | CAT_BREED_TABLE: !Ref DynamoDbCatBreedTable | https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/intrinsic-function-reference-ref.html |
Dynamo DB Local Info:
| Description | Example | More |
|---|---|---|
| Create table |
aws dynamodb create-table –table-name CatBreeds –attribute-definitions AttributeName=CatBreedId,AttributeType=S –key-schema AttributeName=CatBreedId,KeyType=HASH –provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5 –endpoint-url http://192.168.0.31:8000 |
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tools.CLI.html |
| List Tables | aws dynamodb list-tables –endpoint-url http://192.168.0.31:8000 | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tools.CLI.html |
| List All Rows in Table | aws dynamodb scan –table-name PestinatorTable –endpoint-url http://192.168.0.31:8000 | https://stackoverflow.com/a/52236600/522859 |
Node.js Info:
| Description | Example | More |
|---|---|---|
| Run tests | npm test | – |
Hi everyone,
I ran into the following CodeBuild error after upgrading my build environment from the default nodejs8.10 to nodejs10.14:
4: /codebuild/output/tmp/script.sh: pip: not found
This one was a little confusing, but thankfully fairly easy to fix. In your buildspec.yml file update the pip steps to reference pip3 instead of pip:
// Original
commands:
# Install dependencies needed for running tests
- npm install
# Upgrade AWS CLI to the latest version
- pip install --upgrade awscli
// Modified
commands:
# Install dependencies needed for running tests
- npm install
# Upgrade AWS CLI to the latest version
- pip3 install --upgrade awscli
Hi everyone,
A quick post on how to parse DynamoDB items into something more readable when using lambda with Node.js:
Original:
console.log(data["Item"]);
{
CatBreedId: { S: '17acbc81-2b4a-462b-be87-bcc49580b1ae'},
Name: { S: 'Cat #1'}
}
Parsed:
console.log(AWS.DynamoDB.Converter.unmarshall(data["Item"]));
{
"CatBreedId": "17acbc81-2b4a-462b-be87-bcc49580b1ae",
"Name": "Cat #1"
}
Official doco is here: https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/DynamoDB/Converter.html
Thanks to the following stackoverflow post for the info: https://stackoverflow.com/a/44536616/522859
Hi everyone,
I ran into the following error while completing an AWS tutorial: https://github.com/aws-samples/aws-serverless-workshops/tree/master/DevOps/2_ContinuousDeliveryPipeline
> uni-api-test@1.0.0 test C:UsersChris-PCsourcereposUniApiuni-api
> echo ‘Error: no test specified’
‘Error: no test specified’
The solution was to add the following line to my package.json file:
Now when running npm test I get the expected test output:
1) Reading Unicorns
errors on missing unicorn data:
AssertionError [ERR_ASSERTION]: 500 == 404
+ expected – actual
-500
+404
at lambda.lambda_handler (testread.spec.js:77:20)
at appread.js:20:10
at Object.get (testread.spec.js:34:33)
at Object.exports.lambda_handler (appread.js:18:13)
at Context. (testread.spec.js:65:16)
npm ERR! Test failed. See above for more details.
Thanks to this link for the answer: https://teamtreehouse.com/community/when-i-run-test-i-am-getting-an-error-that-says-no-test-specified
Hi everyone,
I ran into the following error while trying to start serverless offline:
Solution
It turned out to be because I didn’t have the Java JDK installed.
I expect you’ll have the same problem if the command prompt doesn’t have access to the JAVA_HOME variable or if your JAVA_HOME path isn’t set correctly.
What I Broke - Programming and Web Development 