JBoss EAP 8.1 - Jakarta EE App Server on RHEL 8

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

## Overview

Red Hat JBoss EAP 8.1 is a production-ready Jakarta EE 10application server that delivers the full Java EE programming model - including EJB, JPA, JMS, JAX-RS, CDI, and JSF - on a lightweight, high-performance runtime. This image delivers JBoss EAP fully installed and configured on Red Hat Enterprise Linux 8, so a complete Jakarta EE application server is running within minutes of launch. Skip the hours of manual installation, dependency resolution, and security hardening that a bare RHEL AMI requires.

## Why This Image Over Alternatives

Unlike self-installing EAP on a bare RHEL AMI or running unsupported WildFly, this image eliminates manual JDK installation, EAP configuration, systemd service creation, and credential setup. The standalone-full profile is pre-tuned with all Jakarta EE 10 subsystems enabled. Every instance launches with a unique, automatically generated management password - removing the security risk of shared or default credentials that plague manual deployments. You also receive ongoing expert support from cloudimg, which is unavailable with community-only options.

## Application Server Stack

• JBoss EAP 8.1 running as a systemd service under the standalone-full profile, enabling the full Jakarta EE 10 feature set including the JMS messaging subsystem (ActiveMQ Artemis)
• Java 21 LTS from the RHEL AppStream repository provides the JDK
• Management console available on port 9990
• HTTP listener on port 8080 serves deployed applications

## Security and Network Guidance

Secure First Boot: On first launch, a one-shot systemd service generates a fresh management admin password unique to that instance, registers it via the EAP add-user utility in the ManagementRealm, and stores the plain text value in a root-only file. No shared or default credentials ship in the image.

Recommended Security Group Rules:

• Port 9990(management console) - restrict to your admin IP range or VPN CIDR only
• Port 8080 (HTTP application traffic) - open to application consumers or place behind an ALB
• Port 22 (SSH) - restrict to your bastion or admin IP

Encryption Guidance: Enable EBS encryption on attached volumes for data-at-rest protection. Configure TLS on the EAP HTTPS listener (port 8443) for data in transit. Place the management console (port 9990) in a private subnet or behind a VPN to prevent public exposure.

## Ready To Deploy

The EAP service, standalone-full profile, and per-instance admin account are all prepared at launch. Connect to the management console on port 9990 to deploy WAR and EAR applications, configure datasources, messaging destinations, and security domains. The HTTP listener on port 8080 serves deployed applications immediately.

## Use Cases

• Enterprise Messaging: Financial services teams processing trade orders and settlement messages through JMS via ActiveMQ Artemis at high throughput
• Microservices and REST APIs: SaaS vendors deploying multiple JAX-RS-based services behind an Application Load Balancer for scalable API back ends
• Stateful Enterprise Applications: EJB-based workloads for insurance claims processing, ERP modules, or supply chain orchestration
• JPA Database Applications: Data-intensive applications backed by Amazon RDS or Aurora with JPA connection pooling and transaction management

## cloudimg Support

24/7 technical support by email and live chat. Our engineers provide expert assistance for JBoss EAP deployment, application configuration, datasource setup, JMS messaging, clustering, and performance tuning. Critical issues receive a one-hour average response time.

## Getting Started

1. Launch the AMI and ensure your security group allows inbound on ports 9990, 8080, and 22

2. SSH into the instance and retrieve your unique admin password from the root-only file

3. Access the EAP management console at http://your-instance-ip:9990

4. Deploy your WAR or EAR application via the console or CLI

For a guided deployment walkthrough or to discuss clustering and high-availability configurations, contact cloudimg support.

All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.