Overview
This is a repackaged software product wherein additional charges apply for hardening, security configuration, and support.
WHAT IS WILDFLY
WildFly is an open-source Jakarta EE 10 application server written in Java, the community successor to JBoss Application Server. It runs WAR and EAR applications and implements the full Jakarta EE web and platform profiles: servlets and JSP, JAX-RS REST services, WebSocket, CDI, JPA/Hibernate, Bean Validation, JTA transactions, JMS messaging (ActiveMQ Artemis), and Jakarta Security. It ships a modular, fast-booting runtime with a web management console, a scriptable jboss-cli, a deployment scanner for drop-in deployments, and datasource/connection-pool management. This image runs WildFly in standalone mode with an explicitly sized JVM heap. WildFly is wholly community open source under LGPL-2.1 - distinct from the commercial JBoss EAP - with no open-core feature gating and no vendor lock-in.
WHAT THIS AMI ADDS
Security hardening:
- Standalone mode with a non-root service user and an explicitly sized JVM heap (-Xms/-Xmx)
- Random management admin user generated at first boot (add-user), written to /root/wildfly-credentials.txt (root-only)
- nginx TLS perimeter on port 443 (self-signed certificate, ready for your own CA cert or Let's Encrypt; certbot pre-installed)
- WildFly application HTTP (8080) and the management interface (9990) bound to 127.0.0.1 only
- UFW firewall pre-configured (ports 22 and 443 only)
- fail2ban, auditd, AppArmor pre-configured
- CVE scan - every image is scanned for vulnerabilities before release
OS hardening (CIS Level 1):
- CIS Ubuntu 24.04 LTS Level 1 benchmark applied via ansible-lockdown
- auditd, SSH hardening, Kernel hardening, IMDSv2 enforced
Compliance artifacts:
- SBOM - CycloneDX 1.6 at /etc/lynxroute/sbom.json
- CIS Conformance Report at /etc/lynxroute/cis-report.html
- CIS Tailored Profile at /usr/share/doc/lynxroute/CIS_TAILORED_PROFILE.md
Highlights
- WildFly security baked in: a random management admin password generated at first boot, an nginx TLS perimeter on 443, and the application (8080) and management (9990) ports bound to localhost - unlike bare WildFly AMIs that bind every interface to 0.0.0.0, ship no management user, and serve the console and apps without TLS.
- CIS Level 1 hardened Ubuntu 24.04 LTS: auditd, fail2ban, AppArmor, SSH key-only, IMDSv2 enforced. CVE-scanned before every release. SBOM (CycloneDX) and CIS Conformance Report included.
- Full Jakarta EE 10 application server: deploy WAR/EAR apps with servlets, JAX-RS, CDI, JPA/Hibernate, and messaging, managed via the web console and jboss-cli. LGPL-2.1 license - fully auditable, no vendor lock-in.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Cost/hour |
|---|---|
t3.medium Recommended | $0.02 |
t3.large | $0.03 |
t3.small | $0.02 |
m6i.large | $0.03 |
Vendor refund policy
We do not offer refunds for this product. AWS infrastructure charges (EC2, EBS, data transfer) are billed separately by AWS and are not refundable by us.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
WildFly 40.0.0.Final - Initial release (June 2026)
- WildFly 40.0.0.Final on Ubuntu 24.04 LTS
- CIS Level 1 hardening applied (ansible-lockdown/UBUNTU24-CIS)
- CVE-scanned before every release
- Standalone mode, non-root service user, explicitly sized JVM heap
- Random management admin user generated at first boot
- nginx TLS perimeter on 443; application (8080) and management (9990) bound to localhost
- UFW firewall pre-configured (ports 22, 443 only)
- fail2ban, auditd, AppArmor pre-configured
- SBOM (CycloneDX 1.6) at /etc/lynxroute/sbom.json
- CIS Conformance Report (OpenSCAP) at /etc/lynxroute/cis-report.html
- IMDSv2 enforced
Additional details
Usage instructions
- Launch instance (t3.medium recommended; t3.small minimum)
- Open Security Group - allow TCP 443 from your IP
- SSH: ssh -i key.pem ubuntu@YOUR_INSTANCE_IP
- Read credentials: sudo cat /root/wildfly-credentials.txt
- Open YOUR_INSTANCE_IP in your browser (HTTPS) - accept the self-signed certificate warning; the WildFly welcome page confirms the server is running
- Deploy your application by copying a .war or .ear file into /opt/wildfly/standalone/deployments/ - the deployment scanner deploys it automatically
The management console listens on 127.0.0.1:9990 and is not exposed. Reach it with an SSH tunnel: ssh -i key.pem -L 9990:127.0.0.1:9990 ubuntu@YOUR_INSTANCE_IP then open 127.0.0.1:9990 in your browser and log in with the management user from the credentials file. Local CLI access: sudo -u wildfly /opt/wildfly/bin/jboss-cli.sh --connect Credentials are saved to /root/wildfly-credentials.txt at first boot. For production, replace the self-signed certificate with your own domain: run sudo certbot --nginx.
Resources
Vendor resources
Support
Vendor support
Visit us online: https://lynxroute.com
For WildFly documentation: https://docs.wildfly.org For WildFly upstream issues:
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.