Listing Thumbnail

    Apache Tomcat 11 - Hardened Jakarta EE Servlet & JSP Application Server

     Info
    Sold by: Lynxroute 
    Deployed on AWS
    Free Trial
    This product has charges associated with it for hardening, security configuration, and support. Apache Tomcat 11 is the reference open-source implementation of the Jakarta EE Servlet, JSP, Expression Language and WebSocket specifications (the jakarta.* namespace, Java 17+). Unlike bare Tomcat AMIs that bind port 8080 to all interfaces, ship the insecure examples webapp, and leave the Manager exposed with a default password, this Lynxroute build is hardened out of the box: the HTTP connector is bound to loopback behind an nginx TLS perimeter on 443, the Manager and Host-Manager apps are firewalled off the public side and protected by a password generated at first boot, the insecure examples webapp is removed, the JVM heap is auto-sized to the instance, and the base is CIS Level 1 hardened Ubuntu 24.04 LTS. Apache-2.0 license - fully auditable, no vendor lock-in.

    Overview

    This is a repackaged software product wherein additional charges apply for hardening, security configuration, and support.

    WHAT IS APACHE TOMCAT

    Apache Tomcat is the world's most widely deployed Java application server and the reference implementation of the Jakarta EE Servlet, JSP, Expression Language, WebSocket and Authentication specifications, maintained by the Apache Software Foundation. Tomcat 11 targets Jakarta EE 11 (the jakarta.* namespace, not the legacy javax.*) and requires Java 17 or newer. It runs servlet/JSP web applications and WAR files with a small footprint, fast startup and a mature, battle-tested codebase. This image ships the official Apache binary distribution (verified against the upstream SHA-512 checksum) running on OpenJDK 17, as a non-root service. Apache-2.0 license, no vendor lock-in.

    WHAT THIS AMI ADDS

    Security hardening:

    • HTTP connector bound to 127.0.0.1:8080 (loopback only); nginx terminates TLS on port 443 and reverse-proxies to it - port 8080 is never exposed
    • Manager and Host-Manager webapps are never reachable from the internet (nginx returns 403 at the perimeter, and Tomcat additionally restricts them to localhost connections)
    • Manager admin password generated uniquely at first boot, written to /root/tomcat-credentials.txt (mode 600)
    • The insecure bundled "examples" webapp (sample servlets with known demo vulnerabilities) is removed
    • Runs as a non-root tomcat system user with UMask 0027
    • JVM heap (-Xms/-Xmx) auto-sized to the instance RAM at first boot
    • UFW firewall pre-configured (only ports 22 and 443 open)
    • certbot pre-installed - one command swaps the self-signed cert for a CA-signed one
    • 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, fail2ban, AppArmor, SSH key-only, 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

    • Tomcat security baked in: the HTTP connector is bound to loopback behind an nginx TLS perimeter on 443, the Manager and Host-Manager apps are firewalled off the public side and protected by a password generated at first boot, and the insecure examples webapp is removed - unlike bare Tomcat AMIs that bind 8080 to all interfaces and leave the Manager exposed.
    • 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.
    • Official Apache Tomcat 11 on OpenJDK 17, Jakarta EE 11 (jakarta.* namespace). Drop a WAR into /opt/tomcat/webapps to deploy. JVM heap auto-sized to your instance. Apache-2.0 license - fully auditable, no vendor lock-in.

    Details

    Delivery method

    Delivery option
    64-bit (x86) Amazon Machine Image (AMI)

    Latest version

    Operating system
    Ubuntu 24.04

    Deployed on AWS
    New

    Introducing multi-product solutions

    You can now purchase comprehensive solutions tailored to use cases and industries.

    Multi-product solutions

    Features and programs

    Financing for AWS Marketplace purchases

    AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
    Financing for AWS Marketplace purchases

    Pricing

    Free trial

    Try this product free for 5 days according to the free trial terms set by the vendor. Usage-based pricing is in effect for usage beyond the free trial terms. Your free trial gets automatically converted to a paid subscription when the trial ends, but may be canceled any time before that.

    Apache Tomcat 11 - Hardened Jakarta EE Servlet & JSP Application Server

     Info
    Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time.
    Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator  to estimate your infrastructure costs.

    Usage costs (3)

     Info
    Dimension
    Cost/hour
    t3.medium
    Recommended
    $0.02
    t3.large
    $0.03
    t3.small
    $0.02

    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?

    Tell us how we can improve this page, or report an issue with this product.
    Tell us how we can improve this page, or report an issue with this product.

    Legal

    Vendor terms and conditions

    Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .

    Content disclaimer

    Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.

    Usage information

     Info

    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

    Apache Tomcat 11.0.22 - Initial release (June 2026)

    • Apache Tomcat 11.0.22 on Ubuntu 24.04 LTS (OpenJDK 17, Jakarta EE 11)
    • CIS Level 1 hardening applied (ansible-lockdown/UBUNTU24-CIS)
    • CVE-scanned before every release
    • HTTP connector bound to 127.0.0.1:8080; nginx terminates TLS on port 443
    • Manager / Host-Manager never exposed on the public perimeter; admin password generated at first boot
    • Insecure bundled examples webapp removed; runs as non-root tomcat user (UMask 0027)
    • JVM heap auto-sized to the instance RAM at first boot
    • certbot pre-installed for CA-signed TLS certificates
    • 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

    1. Launch instance (t3.medium recommended; t3.small minimum)
    2. Open Security Group - allow TCP 443 from your IP
    3. SSH: ssh -i key.pem ubuntu@<PUBLIC_IP>
    4. Read credentials: sudo cat /root/tomcat-credentials.txt
    5. Open https://<PUBLIC_IP>/ in your browser - accept the self-signed certificate warning. The default Tomcat landing page (ROOT app) is served over TLS.
    6. Deploy your own application: copy a .war file into /opt/tomcat/webapps/ (for example myapp.war auto-deploys), then browse https://<PUBLIC_IP>/myapp/
    7. Manage Tomcat via the Manager app (bound to localhost, never exposed on 443) over an SSH tunnel: ssh -i key.pem -L 8080:127.0.0.1:8080 ubuntu@<PUBLIC_IP> open http://127.0.0.1:8080/manager/html  (user admin, password from the credentials file)

    Tomcat's HTTP connector is bound to 127.0.0.1:8080; nginx terminates TLS on port 443 and reverse-proxies to it. The Manager admin password is generated at first boot and saved to /root/tomcat-credentials.txt. The JVM heap is sized automatically from the instance RAM.

    Replace the self-signed TLS certificate with a CA-signed certificate for production use: sudo certbot --nginx -d yourdomain.com

    Resources

    Vendor resources

    Support

    Vendor support

    Visit us online: https://lynxroute.com 

    For Tomcat documentation: https://tomcat.apache.org/tomcat-11.0-doc/  For Tomcat 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.

    Similar products

    Customer reviews

    Ratings and reviews

     Info
    0 ratings
    5 star
    4 star
    3 star
    2 star
    1 star
    0%
    0%
    0%
    0%
    0%
    0 reviews
    No customer reviews yet
    Be the first to review this product . We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.