Hardened ActiveMQ Classic 6.2 on Ubuntu 26.04 LTS

This product provides the final-manifest ActiveMQ Classic version, Java runtime, Ubuntu 26.04 LTS release, broker configuration, and connector exposure as an Amazon Machine Image (AMI) by Hanwei. It applies a versioned operating-system and broker security baseline, records build-date package state, and contains no customer credentials or account-specific configuration.

Marketplace software charges cover Hanwei's broker and operating-system integration, application of the verified security baseline, credential-safe broker preparation, build-date package recording, repeatable AMI construction, and bounded EC2/broker testing. Hanwei support is supplementary and is not the sole basis for Marketplace software charges. AWS infrastructure and disclosed third-party charges are billed separately.

• Broker/runtime integration: The final manifest identifies the ActiveMQ Classic artifact, Java runtime, Ubuntu release, architecture, service account/unit, configuration and data paths, permissions, and configured connectors.
• Security and credential-safe preparation: Hanwei records the verified hardening controls/exceptions and deploys no reusable management password, broker password, private key, cloud credential, or customer secret. The release record identifies the verified per-deployment credential initialization or trusted external-secret method, rotation, and recovery path.
• Repeatable construction and bounded testing: Final-image checks cover launch/restart, broker service, configured connectors and console, credential initialization, authentication/authorization, TLS when configured, storage state, permissions, and secret absence on the recorded EC2 baseline.

• ActiveMQ Classic is an open-source Java message broker. Upstream protocols and JMS-related APIs are distinct from Hanwei's AMI integration, configuration, construction, and testing.
• Connector availability depends on final broker configuration. The manifest identifies enabled connectors, bind addresses, ports, TLS, authentication/authorization, and tested client scope. No connector is published as exposed or generally suitable for clients without final-AMI verification.
• Customers must restrict management and broker listeners to approved networks. Public exposure, anonymous access, shared credentials, predictable credentials, unauthenticated protocols, and unverified TLS are outside this listing's scope.
• Messaging semantics and client behavior depend on broker and client configuration. This listing makes no universal delivery, ordering, protocol, reliability, performance, or security outcome claim.

• The final manifest identifies the persistence adapter, broker data/log paths, owning user, filesystem, mount, EBS mapping, capacity, and shutdown/restart behavior. A data directory alone is not a backup or recovery design.
• Persistence, message durability, EBS storage, encryption, snapshot, backup, restore, replication, shared-store, network-of-brokers, failover, high availability, and disaster recovery are published only when configured and tested. A single AMI does not imply a multi-node deployment. Customers must test workload-appropriate backup, restore, upgrade, rollback, capacity, message-recovery, and failure procedures.

• Ubuntu 26.04 LTS standard support is scheduled through April 2031; coverage beyond this requires applicable Ubuntu Pro or Extended Security Maintenance.
• The final manifest identifies the Java runtime, artifact source/checksum/signature state, Ubuntu repositories, installed packages, and build-date update state. It is not a continuous-currentness claim.
• The final release record identifies verified default user, SSH key injection/login, password/root/sudo state, cloud-init, firewall, and listeners. Update automation, if present, must identify its policy, schedule, scope, exclusions, restart behavior, and test results; it does not guarantee installation success, broker compatibility, or current state after launch.

Customers configure IAM, networking, security groups, certificates, secrets, identities, TLS, monitoring, logging, broker/client settings, patching, backup, and recovery. Applications, protocols, clients, instance types, reliability, performance, scale, availability, compliance, backup restoration, and disaster recovery require customer validation and are not implied unless separately tested.

ActiveMQ Classic is subject to its applicable Apache license and notice requirements. Ubuntu, Java, ActiveMQ, Apache, AWS, and other names and marks identify software or platform context only and do not imply endorsement of Hanwei. Hanwei must complete artifact, dependency, license, NOTICE, trademark, and redistribution review before publication.