Red Hat JBoss EAP 8.0 on RHEL 9 — AWS Marketplace

Red Hat JBoss Enterprise Application Platform (JBoss EAP) 8.0.0.GA preinstalled on Red Hat Enterprise Linux 9, running the standalone-full Jakarta EE 10 profile with Java 17 LTS.

This is one variant of the cloudimg Red Hat JBoss EAP listing. For a different EAP version, return to all JBoss EAP versions →.

• HTTP application port: 8080
• Management console port: 9990
• JBoss home: /opt/jboss-eap-8.0
• Systemd service: jboss-eap.service
• Server log: /opt/jboss-eap-8.0/standalone/log/server.log

---

Prerequisites

• An AWS account with an EC2 key pair
• Security group with inbound rules for TCP 22 (SSH), TCP 8080 (HTTP), and TCP 9990 (Management Console)
• The instance type m5.large or larger is recommended for production workloads

---

Step 1: Connect via SSH

Connect as ec2-user using your EC2 key pair:

ssh -i your-key.pem ec2-user@<instance-public-ip>

---

Step 2: Retrieve the management admin credentials

On first boot, a jboss-eap-firstboot.service generates a unique admin password and writes it to /root/jboss-eap-credentials.txt:

sudo cat /root/jboss-eap-credentials.txt

Expected output:

jboss.admin.user=admin
jboss.admin.pass=<your-unique-password>
jboss.management.url=http://172.31.89.75:9990
jboss.http.url=http://172.31.89.75:8080

---

Step 3: Verify the JBoss EAP service

systemctl status jboss-eap.service

Expected output:

● jboss-eap.service - Red Hat JBoss EAP 8.0
     Loaded: loaded (/etc/systemd/system/jboss-eap.service; enabled; preset: disabled)
     Active: active (running) since Sat 2026-06-06 12:02:52 UTC; 38s ago
   Main PID: 4689 (standalone.sh)
      Tasks: 75 (limit: 21401)
     Memory: 344.5M (peak: 354.3M)

Check that EAP has started fully:

grep 'WFLYSRV0025' /opt/jboss-eap-8.0/standalone/log/server.log | tail -1

Expected output:

2026-06-06 12:02:58,917 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 8.0.0.GA (WildFly Core 21.0.5.Final-redhat-00001) started in 6169ms - Started 320 of 562 services (333 services are lazy, passive or on-demand) - Server configuration file in use: standalone-full.xml

Confirm the Java runtime:

java -version

Expected output:

openjdk version "17.0.19" 2026-04-21 LTS
OpenJDK Runtime Environment (Red_Hat-17.0.19.0.10-1) (build 17.0.19+10-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-17.0.19.0.10-1) (build 17.0.19+10-LTS, mixed mode, sharing)

---

Step 4: Access the Management Console

Open a browser and navigate to:

http://<instance-public-ip>:9990/console

Sign in with: - Username: admin - Password: the value of jboss.admin.pass in /root/jboss-eap-credentials.txt

The Management Console homepage shows Deployments, Configuration, Runtime, Update Manager, and Access Control sections.

---

Step 5: Deploy a sample application via the Management Console

1. Open the Management Console at http://<instance-public-ip>:9990/console
2. Click Deployments in the top navigation
3. Click + (Add Deployment) and upload your WAR or EAR file
4. Enable the deployment — it will be available immediately at http://<instance-public-ip>:8080/<context-root>

Deploy via the CLI

You can also deploy from the command line using jboss-cli.sh:

sudo -u jboss /opt/jboss-eap-8.0/bin/jboss-cli.sh --connect \
  --command="deploy /path/to/<your-app>.war"

List deployed applications:

sudo -u jboss /opt/jboss-eap-8.0/bin/jboss-cli.sh --connect --command="deployment-info"

---

Step 6: Service management

Start, stop, and restart the JBoss EAP service:

sudo systemctl start jboss-eap.service
sudo systemctl stop jboss-eap.service
sudo systemctl restart jboss-eap.service

The service is enabled by default and starts automatically on reboot.

---

Step 7: JNDI and datasource configuration

JBoss EAP 8.0 ships with the standalone-full.xml profile which includes the JMS messaging subsystem (ActiveMQ Artemis). View available JNDI bindings:

sudo -u jboss /opt/jboss-eap-8.0/bin/jboss-cli.sh --connect \
  --command="/subsystem=naming:jndi-view"

To add a datasource, use the Management Console under Configuration → Subsystems → Datasources, or via the CLI. You will need to deploy the appropriate JDBC driver JAR first.

---

Log locations

Log	Path
Server log	/opt/jboss-eap-8.0/standalone/log/server.log
GC log	/opt/jboss-eap-8.0/standalone/log/gc.log
Audit log	/opt/jboss-eap-8.0/standalone/log/audit.log
Firstboot log	/var/log/jboss-eap-firstboot.log

Follow the server log in real time:

sudo tail -f /opt/jboss-eap-8.0/standalone/log/server.log

---

Key paths

Resource	Path
JBoss home	/opt/jboss-eap-8.0
Standalone configuration	/opt/jboss-eap-8.0/standalone/configuration/standalone-full.xml
Deployment directory	/opt/jboss-eap-8.0/standalone/deployments
CLI tool	/opt/jboss-eap-8.0/bin/jboss-cli.sh
Admin credentials	/root/jboss-eap-credentials.txt
Systemd unit	/etc/systemd/system/jboss-eap.service

---

Screenshots

Terminal showing JBoss EAP 8.0.0.GA version information and active systemd service status on RHEL 9.

The JBoss EAP 8.0 Management Console login page served on port 9990.

The JBoss EAP 8.0 Management Console home page showing server status, deployments, and subsystem configuration.

---

Support

This product includes 24/7 technical support from cloudimg. For assistance with JBoss EAP deployment, application configuration, datasource setup, JMS messaging, clustering, or performance tuning, contact us at support@cloudimg.co.uk.