EC2 Guide: Further updates related to the change in script paths for example configurations

There are a couple follow-up changes that should be made in the EC2 Guide now that the script paths for example configurations have been updated:

1) In the section "To launch clustered AMIs with VPC and mod_cluster", the note under the fourth step is a bit out of date now because the example standalone-ec2-ha.xml file no longer includes the example outbound-socket-binding configuration. We should update this note to something like the following:

Note: An /opt/rh/eap7/root/usr/share/wildfly/docs/examples/configs/standalone-ec2-ha.xml example configuration file has been provided. You need to configure a list of proxies in the modcluster subsystem.

Just as an example for reference, a list of proxies can be added as follows:

• Define an outbound-socket-binding called "mod-cluster-proxy1" with an appropriate host and port:

          <outbound-socket-binding name="mod-cluster-proxy1">
              <remote-destination host="${jboss.modcluster.proxy1.host}" port="${jboss.modcluster.proxy1.port}"/>
          </outbound-socket-binding>
  

• Set the proxies attribute in the modcluster subsystem to "mod-cluster-proxy1".

2) In the section "LAUNCH CLUSTERED JBOSS EAP AMIS (WITHOUT MOD_CLUSTER AND VPC", we mention that the example standalone-ec2-ha.xml file sets the instance-id in the undertow subsystem. This is now out of date since the example standalone-ec2-ha.xml file no longer does this. We should update this paragraph to something like the following:

A unique instance-id needs to be set for each standalone server instance in the undertow subsystem. A value for the instance-id can be set manually by editing standalone-ec2-ha.xml or using the CLI. As an example, you can set instance-id="${jboss.jvmRoute}". A value for jboss.jvmRoute can then be specified in standalone.conf using the JAVA_OPTS variable.