JBoss EAP 8.0

Connect to the instance as ec2-user with your EC2 key pair:

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

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

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

Check that the service is active:

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)

Confirm 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 version:

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)

Open a browser and go to:

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

Sign in with these credentials:

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

The Management Console home page shows the Deployments, Configuration, Runtime, Update Manager and Access Control sections.

• Open the Management Console at http://<instance-public-ip>:9990/console.
• Click Deployments in the top navigation.
• Click + (Add Deployment) and upload your WAR or EAR file.
• Enable the deployment. It is available immediately at http://<instance-public-ip>:8080/<context-root>.

Deploy with the CLI

You can also deploy from the command line with 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"

Start, stop or restart the JBoss EAP service with systemd:

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

The service is enabled by default, so it starts automatically on reboot.

JBoss EAP 8.0 ships with the standalone-full.xml profile, which includes the JMS messaging subsystem (ActiveMQ Artemis). List the 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, open Configuration, then Subsystems, then Datasources in the Management Console, or use the CLI. Deploy the appropriate JDBC driver JAR first.