Red Hat JBoss EAP 8.1 base on Windows Server 2022 on AWS User Guide
Overview
This guide covers launching and using the Red Hat JBoss EAP 8.1 base on Windows Server 2022 | cloudimg AMI on Amazon EC2, sold on AWS Marketplace as its own listing. To use it, subscribe to the listing and launch the image as described below.
This image contains no Red Hat software and includes no Red Hat subscription. It is a hardened, fully patched Windows Server 2022 Datacenter server prepared for Red Hat JBoss Enterprise Application Platform (JBoss EAP) 8.1. You install JBoss EAP 8.1 yourself, with your own active Red Hat subscription that includes JBoss EAP, using the installer helper on the image. The helper downloads JBoss EAP from Red Hat with your Red Hat service account (or installs a zip you downloaded from the Red Hat Customer Portal), checks it against the SHA-256 checksum Red Hat publishes, and applies cloudimg's hardened configuration. Your Red Hat credentials are used once and never stored. JBoss EAP then runs under the terms of your agreement with Red Hat.
Pricing: $0.04 per vCPU per hour for the cloudimg image, the same rate on every instance type this listing offers (an m5.large has 2 vCPUs, so $0.08 per hour), plus AWS infrastructure charges. The Microsoft Windows Server 2022 Datacenter licence is included in the Amazon EC2 instance charge. Your Red Hat subscription is separate, under your agreement with Red Hat.
Red Hat support scope. Windows Server 2022 with the Eclipse Temurin (Adoptium) JDK 21 is among the configurations Red Hat lists as tested for JBoss EAP 8.1. Before you rely on Red Hat support for JBoss EAP on this image, check Red Hat's JBoss EAP 8 Supported Configurations article and your subscription terms, or ask your Red Hat account team.
The cloudimg image adds:
- An installer helper,
cloudimg-install-jboss-eap. It downloads JBoss EAP 8.1 from the Red Hat Downloads API with your Red Hat service account (the same API Red Hat's own Ansible collection for JBoss EAP uses), or installs a zip you downloaded from the Red Hat Customer Portal, verifies the checksum, unpacks it intoC:\jboss-eapand registers it as the Windows serviceJBossEAP8. - HTTPS on port 8443 from the moment EAP is installed. First boot creates a TLS key and certificate unique to your instance, for its public DNS name, inside a PKCS12 keystore with its own password. The helper wires it into EAP's HTTPS listener (TLS 1.2 and 1.3) and removes the default keystore that EAP ships with the password
password. - A management password unique to your instance. First boot generates the password of the EAP management user
adminand writes it toC:\ProgramData\cloudimg\jboss-eap\credentials.txt, which only SYSTEM and the Administrators group can read. No password is baked into the image. - Management on localhost only. The management console and CLI (ports 9990 and 9993), the plain HTTP listener (8080) and every other EAP socket listen on
127.0.0.1. Only HTTPS 8443 is reachable from the network; you reach the console from a browser inside your Remote Desktop session or through an AWS Systems Manager port forward. - No demo content. The welcome page and the example H2 datasource (
ExampleDS, usersa) are removed. - A least-privilege service. EAP runs as the virtual service account
NT SERVICE\JBossEAP8, not as SYSTEM. It can read the server code and the instance keystore, and write only thestandaloneruntime directories (configuration,data,deployments,log,tmp); it cannot readcredentials.txt. Windows Firewall rules block the service from the instance metadata service (169.254.169.254 and fd00:ec2::254), so an application flaw cannot be turned into a theft of instance role credentials; the AMI requires IMDSv2. - A firewall that opens 8443 only when there is something to serve. The image ships a Windows Firewall rule for TCP 8443, disabled. The helper enables it after a successful install and disables it again on uninstall, so a fresh instance accepts inbound Remote Desktop (3389) only.
- Fail closed. The
JBossEAP8service refuses to start until first boot has created the keystore and the password and EAP has been installed by the helper with its per instance administrator. - The Microsoft Security Baseline for Windows Server 2022 (Member Server), applied with LGPO and audited by HardeningKitty, with the same reviewed waivers for EC2 as the cloudimg Windows Server 2022 image. The audit report ships in
C:\ProgramData\cloudimg\baseline\. - Fully patched Windows Server 2022 at build time. Windows Update stays on.
What is on the image: Windows Server 2022 Datacenter, Eclipse Temurin JDK 21.0.13 (JAVA_HOME and PATH set machine-wide), Apache Commons Daemon procrun 1.6.1 (the service runner Red Hat's own service.bat uses for EAP on Windows), EC2Launch v2, the AWS Systems Manager agent and the cloudimg tools in C:\Program Files\cloudimg\jboss-eap\. C:\jboss-eap is empty until you install JBoss EAP.
Default user: Administrator (Remote Desktop) · Architecture: x86_64 · Recommended instance type: m5.large
Prerequisites
- An active Red Hat subscription that includes Red Hat JBoss Enterprise Application Platform, and a Red Hat service account in that organisation (a client ID and client secret, created in Step 6). Without them the image can still be launched, but JBoss EAP cannot be downloaded.
- An AWS account subscribed to the listing, an EC2 key pair (you need its private key to read the Administrator password) and a subnet with outbound HTTPS to the internet (the instance downloads EAP from
sso.redhat.comandapi.access.redhat.com). - A security group that allows TCP 3389 (Remote Desktop) and TCP 8443 (your applications over HTTPS) from your own networks only. Never open 9990, 9993, 8080 or 5985 to the network.
- Optional: an instance profile with the
AmazonSSMManagedInstanceCorepolicy, and the AWS CLI with the Session Manager plugin on your computer, if you want to reach the management console or a PowerShell session through AWS Systems Manager.
Step 1: Launch the instance
Open the Red Hat JBoss EAP 8.1 base on Windows Server 2022 | cloudimg listing on AWS Marketplace and choose View purchase options, then Subscribe. Once the subscription is active, choose Launch your software, then Launch from EC2 Console (or One-click launch from AWS Marketplace) and your Region. The Version is Red Hat JBoss EAP 8.1 base on Windows Server 2022 followed by the UTC date and time the build was added (as YYYYMMDDHHMM, for example - 202611151920); if more than one is offered, choose the newest. Choose m5.large (or larger for your applications), your key pair and a security group as above. The software charge is $0.04 per vCPU per hour on every instance type, plus AWS infrastructure charges.
With the AWS CLI on your computer (replace the values in angle brackets; leave out --iam-instance-profile if you do not use Systems Manager):
aws ec2 run-instances --region <region> --image-id <ami-id> --instance-type m5.large \
--key-name <your-key-pair> --security-group-ids <your-security-group> --subnet-id <your-subnet> \
--iam-instance-profile Name=<your-ssm-instance-profile> \
--metadata-options HttpTokens=required,HttpEndpoint=enabled \
--tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=jboss-eap-81-windows}]'
Wait about four minutes after the instance is running: Windows finishes its first boot, EC2Launch sets the Administrator password and the cloudimg first-boot task creates the instance's keystore and management password.
Step 2: Get the Administrator password
In the EC2 console select the instance, choose Actions, Security, Get Windows password, upload the private key of the key pair you launched with and choose Decrypt password. Or with the AWS CLI on your computer:
aws ec2 get-password-data --region <region> --instance-id <instance-id> \
--priv-launch-key <your-key.pem> --query PasswordData --output text
An empty result means Windows has not finished setting the password yet; try again a minute later. Every instance has a different password.
Step 3: Connect over Remote Desktop
Connect to the instance's public DNS name or IP address on port 3389 with a Remote Desktop client that supports Network Level Authentication (Microsoft Remote Desktop on Windows and macOS, FreeRDP on Linux), as user Administrator with the password from Step 2. Each instance creates its own self-signed Remote Desktop certificate on first boot, so your client asks you to trust it the first time.
Open Windows PowerShell as administrator (right-click Windows PowerShell, Run as administrator). Every PowerShell command in this guide runs in that elevated window.
If you launched with a Systems Manager instance profile, you can also open a PowerShell session without Remote Desktop:
aws ssm start-session --region <region> --target <instance-id>
Step 4: Read your instance's values
First boot runs once. It writes the per instance values to C:\ProgramData\cloudimg\jboss-eap\credentials.txt as KEY=VALUE lines: JBOSS_EAP_HOSTNAME, JBOSS_EAP_ADMIN_USER (admin), JBOSS_EAP_ADMIN_PASSWORD (24 characters), JBOSS_EAP_KEYSTORE_PASSWORD (32 characters), JBOSS_EAP_HTTPS_URL and JBOSS_EAP_CONSOLE_URL. First boot takes under a minute once Windows is ready; if Test-Path below prints False, wait a minute and run it again. Check that first boot finished and show the values other than the two passwords:
$d = 'C:\ProgramData\cloudimg\jboss-eap'
Test-Path "$d\firstboot.done"
Get-Content "$d\credentials.txt" | Where-Object { $_ -notmatch '_PASSWORD=' }
To see every value, including the management password you sign in to the console with, run Get-Content C:\ProgramData\cloudimg\jboss-eap\credentials.txt. Treat its output as a secret.
The file is readable by SYSTEM and the Administrators group only, never by the EAP service account:
(Get-Acl C:\ProgramData\cloudimg\jboss-eap\credentials.txt).Access |
Select-Object IdentityReference, FileSystemRights, AccessControlType
The host name comes from the instance's EC2 metadata (public DNS name, else public IP, else private IP), never from a request. To use your own DNS name, see Step 11.
Step 5: Run the preflight check
The preflight check needs no credentials. It confirms first boot, that the keystore opens with its password, that JAVA_HOME is a JDK 21, the free disk space, that C:\jboss-eap is empty, and that the instance can reach Red Hat (Red Hat SSO and the Downloads API answer, and refuse a request without credentials). Each check prints one line; the command exits 0 only when every check passes:
cloudimg-install-jboss-eap -Preflight
On a new instance the output looks like this (your free space differs):
Preflight (cloudimg Red Hat JBoss EAP 8.1 base on Windows Server 2022):
PASS first boot completed (per-instance passwords and keystore; log C:\ProgramData\cloudimg\jboss-eap\firstboot.log)
PASS per-instance HTTPS keystore C:\ProgramData\cloudimg\jboss-eap\tls\server.p12 opens with its own password
PASS JAVA_HOME is a JDK 21 or 17 (C:\Program Files\Eclipse Adoptium\jdk-21.0.13.9-hotspot, version 21.0.13)
PASS service runner Apache Commons Daemon procrun 1.6.1 (C:\Program Files\cloudimg\jboss-eap\procrun\prunsrv.exe)
PASS 54.9 GB free on C: (2 GB needed)
PASS C:\jboss-eap is empty (ready for EAP)
PASS Windows Firewall rule 'cloudimg JBoss EAP HTTPS (TCP 8443)' present (enabled: False)
PASS instance metadata blocked for the JBossEAP8 service (outbound firewall rule)
PASS Red Hat SSO reachable (sso.redhat.com, HTTP 401 without credentials)
PASS Red Hat Downloads API reachable (api.access.redhat.com, HTTP 401 without credentials)
Preflight: ready. Next: cloudimg-install-jboss-eap -CredentialsFile <file> (or without it, to be prompted)
You can check Java, the route to Red Hat and the empty EAP folder yourself:
$ProgressPreference = 'SilentlyContinue'
[Environment]::GetEnvironmentVariable('JAVA_HOME', 'Machine')
cmd /c "java -version 2>&1"
Test-NetConnection sso.redhat.com -Port 443 | Select-Object ComputerName, RemotePort, TcpTestSucceeded
Test-NetConnection api.access.redhat.com -Port 443 | Select-Object ComputerName, RemotePort, TcpTestSucceeded
(Get-ChildItem C:\jboss-eap -Force | Measure-Object).Count
java -version prints OpenJDK Runtime Environment Temurin-21.0.13+9 (build 21.0.13+9-LTS), both TcpTestSucceeded values are True and the last line prints 0. If a Red Hat endpoint fails, allow outbound HTTPS (TCP 443) to sso.redhat.com and api.access.redhat.com in your network ACLs, proxy or NAT gateway.
Step 6: Create a Red Hat service account
The helper authenticates to Red Hat with a service account of the Red Hat organisation that holds your JBoss EAP subscription:
- Sign in to the Red Hat Hybrid Cloud Console at
console.redhat.comas an organisation administrator. - Open the Service Accounts page (from the gear icon, under Identity & Access Management) and choose Create service account. Give it a name such as
eap-downloads-aws. - Copy the Client ID and Client secret. Red Hat shows the secret only once.
The service account belongs to the organisation that holds the JBoss EAP subscription and must be allowed to download its software; your organisation administrator manages its access in User Access. Delete or rotate the service account when you no longer need it.
Step 7: Install JBoss EAP 8.1 with your subscription
Option A: answer two prompts (recommended). Run the helper with no options in the elevated PowerShell window inside your Remote Desktop session. The secret is typed into a hidden prompt, is not echoed and never reaches your PowerShell history:
cloudimg-install-jboss-eap
# Red Hat service account client ID: <your-client-id>
# Red Hat service account client secret (hidden): <your-client-secret>
Option B: a credentials file. Create a text file in your own profile folder, which only you, SYSTEM and the Administrators group can read. The helper refuses a file that grants access to anyone else, and overwrites and deletes it after reading. Open it in Notepad, enter the two lines below with your own values, save it and close Notepad:
notepad "$env:USERPROFILE\rh-service-account.txt"
# RH_CLIENT_ID=<your-client-id>
# RH_CLIENT_SECRET=<your-client-secret>
Then run the helper with the file:
cloudimg-install-jboss-eap -CredentialsFile "$env:USERPROFILE\rh-service-account.txt"
Option C: a zip you downloaded yourself. Download Red Hat JBoss Enterprise Application Platform 8.1.0 (jboss-eap-8.1.0.zip) from the Red Hat Customer Portal (Downloads, JBoss Enterprise Application Platform, version 8.1), and note the SHA-256 checksum shown on the download page. Download it in a browser inside the Remote Desktop session, or download it on your computer and copy it across through your Remote Desktop client's drive or clipboard redirection. Then install it:
cloudimg-install-jboss-eap -Archive "$env:USERPROFILE\Downloads\jboss-eap-8.1.0.zip" -Sha256 <sha256-from-portal>
Remove-Item "$env:USERPROFILE\Downloads\jboss-eap-8.1.0.zip"
What the helper does, in order:
- Exchanges your service account for a short-lived access token at
sso.redhat.com. The token stays in memory and is sent only to Red Hat hosts. - Finds the newest JBoss EAP 8.1 zip in the Red Hat Downloads API, downloads it and compares its SHA-256 with the checksum Red Hat publishes for it. A mismatch deletes the file and stops. The helper refuses an archive that is not JBoss EAP 8.1.
- Unpacks it into
C:\jboss-eap(server code owned by Administrators; the service accountNT SERVICE\JBossEAP8can read it and can write only thestandaloneruntime directories). - Applies cloudimg's configuration to
standalone.xmlwith the JBoss CLI: the HTTPS listener on 0.0.0.0:8443 uses your instance's keystore (TLS 1.2 and 1.3); the public and management interfaces are pinned to 127.0.0.1; EAP's default keystore, the welcome content andExampleDSare removed. - Creates the management user
adminwith the password fromcredentials.txt. - Registers and starts the
JBossEAP8service (automatic, delayed start), and enables the Windows Firewall rule for TCP 8443.
If neither a prompt answer nor a credentials file gives the helper your service account, it exits with code 2 and the message no Red Hat credentials. If Red Hat SSO refuses the service account (invalid_client), it exits with code 3 before downloading anything; check the client ID and secret at console.redhat.com, Service Accounts. Nothing is downloaded or stored in either case.
Step 8: Check the service and HTTPS
After the install, check the service, its account, the firewall rule and the listeners:
Get-Service JBossEAP8 | Select-Object Name, Status, StartType
(Get-CimInstance Win32_Service -Filter "Name='JBossEAP8'").StartName
Get-NetFirewallRule -DisplayName 'cloudimg JBoss EAP HTTPS (TCP 8443)' | Select-Object DisplayName, Enabled
Get-NetTCPConnection -State Listen -LocalPort 8443, 8080, 9990, 9993 -ErrorAction SilentlyContinue |
Select-Object LocalAddress, LocalPort | Sort-Object LocalPort
curl.exe -sk -o NUL -w "HTTPS %{http_code}`n" https://localhost:8443/
The service runs as NT SERVICE\JBossEAP8, the 8443 rule is enabled, 8443 listens on 0.0.0.0 and 8080, 9990 and 9993 listen on 127.0.0.1 only. A fresh server answers 404 on HTTPS because the welcome page is removed.
From your computer (the certificate is self-signed for your instance, so a browser shows a warning until you add your own certificate, see Step 11):
curl -k https://<public-dns-name>:8443/
Step 9: Open the management console
Sign in as admin with JBOSS_EAP_ADMIN_PASSWORD from credentials.txt. The console listens on the instance's loopback address only, so use one of these two routes; never open port 9990 to the network.
In the Remote Desktop session. Open http://127.0.0.1:9990/console in Microsoft Edge on the instance. If the instance has no Edge, install it from Microsoft or use the port forward below; Internet Explorer is not suitable for the EAP console.
Through an AWS Systems Manager port forward from your computer. The instance needs an instance profile with the AmazonSSMManagedInstanceCore policy, and your computer the AWS CLI with the Session Manager plugin. No inbound port is opened:
aws ssm start-session --region <region> --target <instance-id> \
--document-name AWS-StartPortForwardingSession \
--parameters '{"portNumber":["9990"],"localPortNumber":["9990"]}'
Keep the command running and browse to http://localhost:9990/console on your computer.
Step 10: Deploy an application
Copy the application into the deployments directory; EAP deploys it within a few seconds and writes a .deployed marker next to it (.failed if it does not deploy). Or use the management CLI on the instance:
Copy-Item .\myapp.war C:\jboss-eap\standalone\deployments\
Get-ChildItem C:\jboss-eap\standalone\deployments\myapp.war*
& C:\jboss-eap\bin\jboss-cli.bat --connect --controller=127.0.0.1:9990 --command="deployment-info"
Your application is then served at https://<public-dns-name>:8443/myapp/.
JVM settings. JVM options (for example the heap, -Xms1g -Xmx2g) go in JAVA_OPTS in C:\jboss-eap\bin\standalone.conf.bat, followed by Restart-Service JBossEAP8. The server runs standalone.xml. To change the HTTPS port or open another listener, change the configuration with jboss-cli.bat and open the port in both the security group and the Windows Firewall.
Step 11: Use your own host name or certificate
To issue the instance certificate for your own DNS name (for example after pointing a Route 53 record at the instance), run:
cloudimg-install-jboss-eap -Hostname eap.example.com
The helper records the name in C:\ProgramData\cloudimg\jboss-eap\hostname.txt, mints a new key and certificate into the keystore with the same keystore password and restarts the service. To use a certificate from your own certificate authority, import it into a PKCS12 keystore and point the cloudimgKS key store in standalone.xml at it, or put an Application Load Balancer with an AWS Certificate Manager certificate in front of port 8443.
Step 12: Keep Windows, Java and EAP up to date
Windows. Windows Update stays on, so Windows installs updates on its own schedule. To see what is pending:
$searcher = (New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher()
$searcher.Search("IsInstalled=0 and IsHidden=0 and Type='Software'").Updates | Select-Object Title
To install them now, use Settings, Windows Update, Check for updates, or sconfig option 6, and restart when Windows asks. The JBossEAP8 service starts again on its own after the restart.
Eclipse Temurin JDK. Temurin does not update itself. Adoptium publishes a JDK 21 update every quarter (January, April, July and October). Download the new Windows x64 JDK 21 MSI from adoptium.net, check its SHA-256 against the one Adoptium publishes, install it with the same features (they set JAVA_HOME and PATH), then restart the service, which reads JAVA_HOME when it starts:
Start-Process msiexec.exe -Wait -ArgumentList '/i', "$env:USERPROFILE\Downloads\<temurin-21-msi-file>.msi", 'ADDLOCAL=FeatureMain,FeatureEnvironment,FeatureJavaHome', '/qn'
[Environment]::GetEnvironmentVariable('JAVA_HOME', 'Machine')
Restart-Service JBossEAP8
JBoss EAP. Apply Red Hat's EAP 8.1 updates with your subscription, as described in Red Hat's guide Updating Red Hat JBoss Enterprise Application Platform: with the JBoss EAP installation manager (jboss-eap-installation-manager, downloaded from the Red Hat Customer Portal) while the service is stopped, or with the management CLI installer update commands. For example, with the installation manager unpacked in C:\jboss-eap-installation-manager:
Stop-Service JBossEAP8
& C:\jboss-eap-installation-manager\bin\jboss-eap-installation-manager.bat update perform --dir C:\jboss-eap
Start-Service JBossEAP8
Windows Firewall and security model
The Windows Firewall is on for every profile with inbound traffic blocked unless a rule allows it. On a fresh instance only Remote Desktop and core networking are allowed in; the 8443 rule exists and stays disabled until the helper installs EAP:
Get-NetFirewallRule -DisplayName 'cloudimg JBoss EAP HTTPS (TCP 8443)' | Select-Object DisplayName, Enabled, Direction, Action
Get-NetFirewallRule -Direction Inbound -Enabled True -Action Allow |
Select-Object DisplayGroup, DisplayName | Sort-Object DisplayGroup, DisplayName
The outbound rules that block the EAP service from the instance metadata service:
Get-NetFirewallRule -Direction Outbound -Action Block | ForEach-Object {
$svc = ($_ | Get-NetFirewallServiceFilter).Service
if ($svc -like 'JBoss*') {
[pscustomobject]@{ Rule = $_.DisplayName; Service = $svc; Enabled = $_.Enabled
RemoteAddress = (($_ | Get-NetFirewallAddressFilter).RemoteAddress -join ', ') }
}
}
| Port | Listens on | Purpose |
|---|---|---|
| 3389 | all interfaces | Remote Desktop with Network Level Authentication, user Administrator |
| 8443 | all interfaces | your applications over HTTPS (after EAP is installed) |
| 8080 | 127.0.0.1 | EAP plain HTTP (loopback only) |
| 9990, 9993 | 127.0.0.1 | EAP management console and CLI |
| 4712, 4713 | 127.0.0.1 | EAP transactions |
The block applies only to the EAP service, so the SSM agent, EC2Launch and Windows still reach instance metadata. If an application genuinely needs AWS credentials, give it explicit credentials rather than removing these rules. The AMI is marked IMDSv2-only.
View the baseline report
The Microsoft Security Baseline audit the build measured ships in C:\ProgramData\cloudimg\baseline\: baseline-report.html (every rule audited and its result, waived rules marked), hardeningkitty-report.csv, baseline-summary.json, waivers.txt and waivers.json (the rules waived for EC2 and why) and tool-versions.json. Show the summary:
Get-Content C:\ProgramData\cloudimg\baseline\baseline-summary.json | ConvertFrom-Json |
Select-Object profile, audited, waived, scored, pass, fail, ratePct, thresholdPct, evaluatedAt
The waived rules are the same as on the cloudimg Windows Server 2022 image: two would stop the Administrator signing in over Remote Desktop, and six belong to the Credential Guard policy, which needs UEFI Secure Boot and cannot run on this legacy BIOS image. The audit is a measurement made by open-source tooling against Microsoft's published baseline, not a certification by Microsoft or any other body.
Uninstall or reinstall
cloudimg-install-jboss-eap -Uninstall
This stops and deletes the JBossEAP8 service, empties C:\jboss-eap, including your deployments, data and logs, and disables the 8443 firewall rule, returning the instance to its base state. Your keystore and management password stay, so you can install again.
Troubleshooting
- Preflight says first boot has not completed: read the first-boot log, which holds no secrets. First boot retries at the next restart, up to three times; a
firstboot.failedfile in the same folder means it gave up. The instance needs IMDSv2 to read its host name, or a name inC:\ProgramData\cloudimg\jboss-eap\hostname.txt.
Get-Content C:\ProgramData\cloudimg\jboss-eap\firstboot.log -Tail 20
no Red Hat credentials(exit code 2): the helper had neither a prompt answer nor a credentials file. Run it in an interactive elevated PowerShell window, or use-CredentialsFile.- Red Hat SSO refuses the service account (exit code 3,
invalid_client): the client ID or secret is wrong, or the service account was deleted. Create a new secret in the Hybrid Cloud Console. - The Red Hat Downloads API refuses the service account: the organisation's subscription does not include JBoss EAP, or the account cannot download it. Ask your Red Hat account team, or use Option C with a zip from the Customer Portal.
- The credentials file is refused: it grants access to someone other than you, SYSTEM or the Administrators group. Create it in your own profile folder as in Option B.
- The service does not start: the start guard refuses until first boot, an install by the helper and a per instance administrator are in place, and names what is missing. Read
C:\jboss-eap\standalone\log\server.logand the System event log (Event Viewer, Windows Logs, System) for theJBossEAP8service. - HTTPS 8443 does not answer from your computer: check that the security group allows TCP 8443 from your address and that the
cloudimg JBoss EAP HTTPS (TCP 8443)rule is enabled (Step 8).
Support
cloudimg's support team is on hand 24 hours a day by email for this image, with a guaranteed response within 24 hours: launch and first login over Remote Desktop, the Administrator password, first boot and the per instance credentials, the installer helper, the JBossEAP8 service, the Windows Firewall, the Microsoft Security Baseline and Windows Update.
- Email: support@cloudimg.co.uk
- Website: www.cloudimg.co.uk/support
- User Guides: www.cloudimg.co.uk/guides
Questions about JBoss EAP itself, its updates and your Red Hat subscription go to Red Hat under your subscription. The Windows Server 2022 Datacenter licence is included in the Amazon EC2 instance charge.
Red Hat and JBoss are trademarks of Red Hat, Inc., registered in the United States and other countries; cloudimg is not affiliated with or endorsed by Red Hat. Eclipse Temurin and Adoptium are trademarks of the Eclipse Foundation. Microsoft and Windows Server are trademarks of the Microsoft group of companies. cloudimg is not affiliated with or endorsed by the Eclipse Foundation or Microsoft.