SecureAnyCloud
Deployment guide

JBoss EAP 8.1

Overview

Red Hat JBoss Enterprise Application Platform (JBoss EAP) is a Jakarta EE application server for running enterprise Java applications. This SecureAnyCloud image provides JBoss EAP 8.1 preinstalled on Red Hat Enterprise Linux 8.10, running the standalone-full Jakarta EE profile with Java 21 LTS.

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

What you get:

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

Prerequisites

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

Connect over SSH

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

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

Retrieve the management admin credentials

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

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

The output looks like this:

jboss.admin.user=admin jboss.admin.pass=f804bc0537fc90c1Aa1#a978 jboss.management.url=http://172.31.91.32:9990 jboss.http.url=http://172.31.91.32:8080
3

Verify the JBoss EAP service

Check that the systemd unit is active:

systemctl status jboss-eap.service

The output looks like this:

● jboss-eap.service - Red Hat JBoss EAP Loaded: loaded (/etc/systemd/system/jboss-eap.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2026-05-27 19:50:30 UTC; 2min ago Main PID: 2049 (standalone.sh) Tasks: 67 (limit: 22525) Memory: 390.1M

Then confirm that EAP has finished starting:

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

The output looks like this:

2026-05-27 19:50:37,870 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 8.1 (WildFly Core 27.1.0.Final-redhat-00010) started in 7396ms - Started 365 of 580 services (338 services are lazy, passive or on-demand) - Server configuration file in use: standalone-full.xml
4

Open the Management Console

Open a browser and go to:

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

Sign in with Username admin and the password from jboss.admin.password in /root/jboss-eap-credentials.txt.

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

5

Deploy an application from the Management Console

  • 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.1/bin/jboss-cli.sh --connect \
  --command="deploy /path/to/<your-app>.war"

List the deployed applications:

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

Manage the service

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 after a reboot.

7

Configure JNDI and datasources

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

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

To add a datasource, use the Management Console under Configuration → Subsystems → Datasources, or use the CLI. Deploy the appropriate JDBC driver JAR first.

Log locations

JBoss EAP writes these log files:

  • Server log: /opt/jboss-eap-8.1/standalone/log/server.log
  • GC log: /opt/jboss-eap-8.1/standalone/log/gc.log
  • Audit log: /opt/jboss-eap-8.1/standalone/log/audit.log
  • First-boot log: /var/log/jboss-eap-firstboot.log

Follow the server log in real time:

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

Key paths

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

Screenshots

A terminal showing JBoss EAP 8.1 version information and the active systemd service status on RHEL 8.

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

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

Support

This image includes 24/7 technical support from SecureAnyCloud. For help with JBoss EAP deployment, application configuration, datasource setup, JMS messaging, clustering or performance tuning, contact us at sales@secureanycloud.com.

Deploy on AWS

Launch JBoss EAP 8.1 on AWS with 24/7 support from SecureAnyCloud.

View on Marketplace

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com

Deploy on AWS