Errata: November 22, 2018

Unless otherwise noted, corrections have been made to all versions.

Thank you for purchasing AWS Lambda in Action. Please post any errors, other than those listed below, in the book's Author Online Forum. We'll update this list as necessary. Thank you!


Page 4, Chapter 1:

The final part of the first paragraph should read:

Even if you use a container-based approach in building the environment, with tools such as Docker, you're still in charge of managing versioning and updates of the containers you use.

Page 34:

--payload "{"""name"":""John""}":

should be:

--payload "{""name"":""John""}"

There's a third double quotation mark preceding name.

Pages 45 and 55

The shortened URL to the API gateway template is wrong. The correct link follows:
https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-mapping-template-reference.html

Page 54, Chapter 3, Section 3.6:

curl https:///prod/users/JohnDoe123/greet

should be:

curl https:///prod/user/JohnDoe123/greet

Page 58, Chapter 3, Section 3.7:

A default syntax to send back HTTP return code, headers, and the body of the response is also put in place. Using this syntax, you only need to work on the Lambda function code and you can leave the configuration in the API Gateway console as it is. The configurations you used in this chapter, using custom mapping templates, are still available.

Page 82, Solution:

The final action is missing the closing double quote, should be:

"Action": [ "s3:GetObject" ],

Page 94, Figure 5.6:

The event type of the trigger should be Object Created (All)

Page 96, Figure 5.7:

The event type of the trigger should be Object Created (All)

Page 125, Solution:

The final resource

"arn:aws:dynamodb:us-east-1:123456789012:table/shared-table"

should read:

"arn:aws:dynamodb:<region>:<account-id>:table/shared-table"
A default syntax to send back HTTP return code, headers, and the body of the response is also put in place. Using this syntax, you only need to work on the Lambda function code, and you can leave the configuration in the API Gateway console as it is. The configurations you used in this chapter, using custom mapping templates, are still available.