User guide

Warning
The above settings are sufficient for this example scenario but for a production environment it is
highly recommended that you consider the failover and back-up features.
It is good practice to create separate user/password pairs for each application accessing the
database. T une other configuration options according to your application's requirements.
6.3. Create a Virtual Private Cloud (VPC)
1. Go to the VPC tab in the AWS console.
2. Subscribe to the service if needed.
3. Click on "Create new VPC".
4. Choose a VPC with one public and one private subnet.
a. Set the public subnet to be 10.0.0.0/24 .
b. Set the private subnet to be 10.0.1.0/24 .
5. Go to Elastic IPs.
6. Create an elastic IP for use by the EWS mod_cluster proxy/NAT instance.
7. Go to Security groups and create a security group to allow all traffic in and out.
8. Go to Network ACLs
a. Create an ACL to allow all traffic in and out.
b. Create an ACL to allow all traffic out and traffic in on only T CP ports 22, 8009, 8080, 84 43
and 16163.
Note
VPC is recommended for a JBoss Enterprise Application Platform cluster setup as it greatly
simplifies secure communication between cluster nodes, a JON Server and the mod_cluster
proxy. Without a VPC all these communication channels need to be encrypted and authenticated.
Please refer to JBoss Enterprise Application Platform for detailed instructions on configuring SSL.
Also note that we are using a database external to the VPC in this example. Your security policies
may require connection to the database to be encrypted. Please refer to Amazon's RDS FAQ for
details about encrypting the database connections.
6.4. Launch a JBoss Enterprise Web Server instance to serve as a
mod_cluster proxy and a NAT instance for the VPC
1. Create an elastic IP for this instance.
2. Select an AMI.
3. Go to Security Group and allow all traffic (use Red Hat Enterprise Linux's built-in firewall
capabilities to restrict access if desired).
4. Choose "running" in the public subnet of the VPC.
5. Choose a static IP (e.g. 10.0.0.4).
6. Put the following in the User Data: field:
Chapter 6. Launching clustered JBoss Enterprise Application Platform instances
17