Chapter 3. Launch a Non-clustered JBoss EAP Instance


This topic lists the steps to launch a non-clustered instance of JBoss EAP on a Red Hat AMI (Amazon Machine Image).

Pre-requisites

  • A suitable Red Hat AMI. Refer to Supported Red Hat AMIs.
  • A pre-configured Security Group that allows incoming requests on at least ports 22, 8080, and 9990.

Launch a Non-Clustered JBoss EAP Instance

Note

You can connect to an EC2 instance through ssh as a ec2-user user. If you need administrative privileges, you can change to root later For example,

$ ssh -l ec2-user ${INSTANCE_PUBLIC_IP}
...
$ sudo su -
Copy to Clipboard Toggle word wrap
  • Launch the Red Hat AMI instance.

    A non-clustered instance of JBoss EAP has been configured, and launched on a Red Hat AMI.

  • To configure JBoss EAP, you can pass arguments to the service directly. Some arguments may not be handled in this way. The location of the service configuration files is:

    • RHEL 6: /etc/sysconfig/eap7-standalone
    • RHEL 7: /etc/opt/rh/eap7/wildfly/eap7-standalone.conf
    Note
    • For system path details, see System Paths.
    • For complex configuration, you can either use the standalone.conf file in the JBoss EAP bin directory: /opt/rh/eap7/root/usr/share/wildfly/bin/, or you can start the JBoss EAP service and configure the server using CLI. The script can be found in the bin directory. Then, reload the configuration.
    • yum -y update should be run regularly, to apply security fixes and enhancements.
  • To start JBoss EAP on RHEL 6, run the following command:

    $ service eap7-standalone start
    Copy to Clipboard Toggle word wrap

    To start JBoss EAP on RHEL 7, run the following command:

    $ systemctl start eap7-standalone
    Copy to Clipboard Toggle word wrap
  • To stop JBoss EAP, run the following command:

    $ service eap7-standalone stop
    Copy to Clipboard Toggle word wrap

    Or

    $ systemctl stop eap7-standalone
    Copy to Clipboard Toggle word wrap
Note

systemctl command is relevant to only RHEL 7.

Note

If you want to bind JBoss EAP to a different IP address, add the following line in the /etc/opt/rh/eap7/wildfly/eap7-standalone.conf file on RHEL 7. The internal IP address is translated into a public IP address by EC2.

WILDFLY_BIND=$YOUR_PRIVATE_IP_ADDRESS
Copy to Clipboard Toggle word wrap
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red Hat
Back to top