Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 4. Launching a non-clustered JBoss EAP instance

This chapter lists the steps to launch a non-clustered instance of JBoss EAP on a Red Hat Amazon Machine Image (AMI) created through a private AMI or public Marketplace listing.

Prerequisites

  • A suitable Red Hat AMI. See Supported Red Hat AMIs for more information.
  • A pre-configured Security Group that allows incoming requests on at least ports 22, 8080, and 9990.
Note

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

$ ssh -l ec2-user ${INSTANCE_PUBLIC_IP}
...
$ sudo su -
Copy to Clipboard

Procedure

  1. Launch the Red Hat AMI instance.

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

Note
  • For complex configuration, you can either use the standalone.conf file in the JBoss EAP bin directory: /opt/rh/eap8/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.
  • You must regularly run the yum -y update to apply security fixes and enhancements.

  1. Start JBoss EAP using the following command: 

    $ systemctl start eap8-standalone
    Copy to Clipboard

  2. Stop JBoss EAP using the following command: 

    $ systemctl stop eap8-standalone
    Copy to Clipboard
Note

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

WILDFLY_BIND=$YOUR_PRIVATE_IP_ADDRESS
Copy to Clipboard
Back to top
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

© 2025 Red Hat