Amazon Web Services in Action Errata

The CloudFormation UI has changed a bit. You now enter the stack name in the 2nd step.

Every CloudFormation template containing a AWS::EC2::VPCGatewayAttachment attaching an Internet Gateway to a VPC requires a DependsOn attribute for every resource with a public IP address.

• Auto Scaling Group
• EC2 Instance
• ELB
• Elastic IP
• VPC routes including the Internet Gateway

See http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-dependson.html#gatewayattachment for more details.

Example templates from various chapters have been improved accordingly:

chapter2/template.json
chapter6/vpc.json
chapter9/template-multiaz.json
chapter9/template-snapshot.json
chapter9/template.json
chapter11/multiaz-ebs.json
chapter11/multiaz-elasticip.json
chapter11/multiaz.json
chapter12/loadbalancer.json
chapter14/url2png-loadtest.json
chapter14/url2png.json
chapter14/wordpress.json
chapter14/wordpress-loadtest.json

Example from chapter 2 chapter2/template.json:

...
"LoadBalancer": {
    "Type": "AWS::ElasticLoadBalancing::LoadBalancer",
    "Properties": {
        "Subnets": [{"Ref": "SubnetA"}, {"Ref": "SubnetB"}],
        "LoadBalancerName": "awsinaction-elb",
        "Listeners": [{
            "InstancePort": "80",
            "InstanceProtocol": "HTTP",
            "LoadBalancerPort": "80",
            "Protocol": "HTTP"
        }],
        "HealthCheck": {
            "HealthyThreshold": "2",
            "Interval": "5",
            "Target": "TCP:80",
            "Timeout": "3",
            "UnhealthyThreshold": "2"
        },
        "SecurityGroups": [{"Ref": "LoadBalancerSecurityGroup"}],
        "Scheme": "internet-facing"
    },
    "DependsOn": "VPCGatewayAttachment"
}
...

Requests using the Elastic IP address will now be routed to virtual server B without interruption

is not correct. It should be:

Requests using the Elastic IP address will now be routed to virtual server B with a short interruption while moving the Elastic IP

PowerShell on Windowso

is not correct. It should be:

PowerShell on Windows

The Node.js version 0.12.* is no longer supported and fails with an error: ConfigurationValidationException Value is not one of the allowed values: [4.6.1, 4.8.0, 5.12.0, 6.9.1, 6.10.0, 7.6.0]

$ aws elasticbeanstalk create-environment --environment-name etherpad --application-name etherpad --option-settings Namespace=aws:elasticbeanstalk:environment,OptionName=EnvironmentType,Value=SingleInstance Namespace=aws:elasticbeanstalk:container:nodejs,OptionName=NodeVersion,Value=0.12.15 --solution-stack-name "$SolutionStackName" --version-label 1.5.2

is not correct. It should be:

$ aws elasticbeanstalk create-environment --environment-name etherpad --application-name etherpad --option-settings "Namespace=aws:elasticbeanstalk:environment,OptionName=EnvironmentType,Value=SingleInstance" --solution-stack-name "$SolutionStackName" --version-label 1.5.2

Code format is broken.

Replace …

$ aws elasticbeanstalk list-available-solution-stacks --output text \
--query "SolutionStacks[?contains(@, 'running Node.js')] | [0]"\
64bit Amazon Linux 2015.03 v1.4.6 running Node.js

with …

$ aws elasticbeanstalk list-available-solution-stacks --output text \
--query "SolutionStacks[?contains(@, 'running Node.js')] | [0]"

Ensuring PowerShell compatibility.

Replace …

$ aws elasticbeanstalk create-application-version --application-name etherpad --version-label 1.5.2 --source-bundle S3Bucket=awsinaction,S3Key=chapter5/etherpad.zip

with …

aws elasticbeanstalk create-application-version --application-name etherpad --version-label 1.5.2 --source-bundle "S3Bucket=awsinaction,S3Key=chapter5/etherpad.zip"

Note: \ as line separator needs to be removed from all code listings as well.

OpsWorks added a new version of Chef as the new default for the service. To be able to follow the example from 5.4.2 you need to use a Chef 11 stack.

Therefore the 12 steps described in CREATING A NEW OPSWORKS STACK need to be replaced with:

1. Click Add Stack under Select Stack or Add Your First Stack.
2. Select Chef 11 stack
3. For Name, type in irc.
4. For Region, choose US East (N. Virginia).
5. The default VPC is the only one available. Select it.
6. For Default Subnet, select us-east-1a.
7. For Default Operating System, choose Ubuntu 14.04 LTS.
8. Select your SSH key, mykey, for Default SSH Key.
9. Select Chef version 11.10
10. Click Add Stack to create the stack.

An IAM role can be used to authenticate AWS resources like virtual servers. You can attach no roles, one role, or multiple roles to an EC2 instance.

is not correct. It should be:

An IAM role can be used to authenticate AWS resources like virtual servers. You can attach up to one role to an EC2 instance.

You may need to install the MySQL client on your machine remove, as it includes these tools.

is not correct. It should be:

You may need to install the MySQL client which comes with the mysqldump tool.

New terminology for primary key attributes was introduced by AWS:

• Hash Key is now called Partition Key
• Range Key is now called Sort Key

Only the names have changed; the functionality remains the same.

See official release notes: https://aws.amazon.com/releasenotes/9068906752066271

No additional traffic charges apply if you use AWS resources like EC2 servers to access DynamoDB in the same region

is not correct. It should be:

No additional traffic charges apply if you use AWS resources like EC2 servers to access DynamoDB in the same region.

The primary key is either a hash or a hash and a range. Hash keys

is not correct. It should be:

The primary key is either a hash or a hash and a range.

When you create a load balancer, AWS starts two instances in the background and uses DNS to distributed between the two.

Is not correct. It should be:

When you create a load balancer, AWS starts two instances in the background and uses DNS to distribute between the two.