In lambda-comments.json, line 145 and 181, change "nodejs" to "nodejs4.3"

[vamworks]

Hi Jim,

My name is Vam. I live in Beijing, China. First of all, I want to say - thank you very much!! I am so so excited when I found your work - It is exactly what I need and it is amazing! You know that Disqus and many other popular sites are blocked in China for some reasons. And I want to have a simple commenting system that can be accessed from China and all over the world. I spent a lot of time tried to find a right one but I didn't. Until I see your Lambda-comments. And I agreed with your point of view from "Introducing lambda-comments". I just integrated it. Please have a look:

http://vamworks.com/2016/paintings-and-drawings-by-me-before-2016/

However, during the process I got a problem: when I create a stack via the command:

npm run create-cloudformation

I saw this message when I check my AWS CloudFormation console:

console of CloudFormation: ROLLBACK_COMPLETE

When click the stack name, I see the following problem from log:

Logical ID:

QueueCommentLambdaFunction

Status reason:

The runtime parameter of nodejs is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs4.3) while creating or updating functions.

I spent some time to did research and finally I found the answer:

http://docs.aws.amazon.com/cli/latest/reference/lambda/create-function.html

In lambda-comments.json, line 145 and 181, change "nodejs" to "nodejs4.3".

After that, it works very well!

:)

Best Regards,

Vam

[metrue]

@vamworks I met the same issue also.
But after updating to nodejs4.3, I met the other issue

	18:04:34 UTC+0800	ROLLBACK_IN_PROGRESS	AWS::CloudFormation::Stack	myBlogComments	The following resource(s) failed to create: [WorkerLambdaFunction, PrivateS3BucketPolicy, QueueCommentLambdaInvokePermission, LambdaRoleInstanceProfile, JobStreamDynamoDBTable, WebsiteS3BucketPolicy]. . Rollback requested by user.

Do you have any idea ?