Revision: 8063173.

The book currently starts off explaining what AMIs are and what kind of AMIs we support. Then it assumes the user has started an AMI and explains how to start EAP on it. This is fine, but there's a gap in the documentation on starting the instance itself.

Strictly said, this does not pertain to EAP, but I suggest adding a small section on how to start an instance in EC2. The section could walk the user through the process. There are two different ways this may be done - through the EC2 management console (clicking the right buttons, https://console.aws.amazon.com/ec2/v2/home) and through the aws command (command line, http://docs.aws.amazon.com/cli/latest/reference/index.html#cli-aws). Libraries like JClouds (https://jclouds.apache.org/) could also get an honorable mention.

User-data field configuration is explained in later chapters. Optionally an example can be provided right away that will start EAP bound to public IP address. This is what we use in our tests:

#!/bin/bash

# platform dependent variables
if [[ "`cat /etc/redhat-release`" = *"release 7"* ]]; then
    SERVICE_CONF_FILE=/etc/opt/rh/eap7/wildfly/eap7-standalone.conf
    START_COMMAND="systemctl start eap7-standalone"
else
    SERVICE_CONF_FILE=/etc/sysconfig/eap7-standalone
    START_COMMAND="service eap7-standalone start"
fi

# set up addresses
INTERNAL_IP_ADDRESS=`ip addr show | grep eth0 -A 2 | head -n 3 | tail -n 1 | awk '{ print $2 }' | sed "s-/24--g" | cut -d'/' -f1`
echo "JAVA_OPTS=\"$JAVA_OPTS -Djboss.bind.address=$INTERNAL_IP_ADDRESS -Djboss.bind.address.private=$INTERNAL_IP_ADDRESS -Djboss.bind.address.management=$INTERNAL_IP_ADDRESS\"" >> /opt/rh/eap7/root/usr/share/wildfly/bin/standalone.conf

# start EAP
$START_COMMAND