apache-activemq-artemis-fips

packaged by Chainguard

Chainguard Container for apache-activemq-artemis-fips

ActiveMQ Artemis is the next generation message broker from Apache ActiveMQ.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/apache-activemq-artemis-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

This is the FIPS variant of the Chainguard apache-activemq-artemis container image, comparable to apache/artemis.

The broker runs on openjdk-fips, where the Bouncy Castle FIPS provider operates in approved-only mode. This changes some behavior compared to the upstream image and the non-FIPS variant:

• The broker does not start with the default ARTEMIS_PASSWORD. On first start the entrypoint exits with an error unless ARTEMIS_PASSWORD is set to a value of at least 14 characters.
• Keystores that hold private keys must be BCFKS.
• Client TLS URLs must set forceSSLParameters=true, otherwise URL parameters such as trustStorePath are ignored.
• Serving the web console over TLS requires http2="false" and a BCFKS keystore on the binding element in bootstrap.xml. With HTTP/2 left enabled, the console fails to start.

Getting Started

The image is deployed as described in the upstream Apache ActiveMQ Artemis documentation, with one addition: ARTEMIS_PASSWORD must be set to at least 14 characters. The following command starts the broker with the instance generated inside the container file system:

docker run --detach --name artemis -p 61616:61616 -p 8161:8161 \
  -e ARTEMIS_PASSWORD=change-this-password \
  cgr.dev/ORGANIZATION/apache-activemq-artemis-fips:latest

To persist the broker instance (journal, configuration, and large-message store) across containers, mount a directory over /var/lib/artemis-instance. The directory must be writable by UID 1001:

docker run --detach --name artemis -p 61616:61616 -p 8161:8161 \
  -e ARTEMIS_PASSWORD=change-this-password \
  -v "${PWD}/artemis-data:/var/lib/artemis-instance" \
  cgr.dev/ORGANIZATION/apache-activemq-artemis-fips:latest

Configuration

A TLS acceptor shows the FIPS-specific keystore and client settings in one place. The examples build on the persistent setup from Getting Started: the broker instance, including all of its configuration, lives in /var/lib/artemis-instance, mounted from ${PWD}/artemis-data on the host. Create a BCFKS keystore in the instance's etc directory with the image's keytool:

docker exec artemis keytool -genkeypair -alias artemis -keyalg RSA -keysize 2048 \
  -sigalg SHA256withRSA -dname "CN=broker.example.com" \
  -ext "SAN=dns:broker.example.com" \
  -keystore /var/lib/artemis-instance/etc/server.bcfks \
  -storetype BCFKS -storepass a-14char-secret -keypass a-14char-secret

Add an acceptor referencing it to the acceptors element of artemis-data/etc/broker.xml (in the container, /var/lib/artemis-instance/etc/broker.xml), then restart the container:

<acceptor name="ssl">tcp://0.0.0.0:61617?sslEnabled=true;keyStorePath=/var/lib/artemis-instance/etc/server.bcfks;keyStorePassword=a-14char-secret;keyStoreType=BCFKS</acceptor>

Clients then connect with the trust store parameters forced onto the URL:

tcp://broker.example.com:61617?sslEnabled=true&forceSSLParameters=true&trustStorePath=/path/to/trust.bcfks&trustStorePassword=a-14char-secret&trustStoreType=BCFKS

The broker negotiates FIPS-approved TLS 1.2 and 1.3 cipher suites and refuses non-approved suites from either side of the connection.

To serve the web console over TLS, reuse the keystore on the existing binding element of artemis-data/etc/bootstrap.xml and disable HTTP/2, which otherwise prevents startup:

<binding name="artemis" uri="https://0.0.0.0:8161" http2="false"
    keyStorePath="/var/lib/artemis-instance/etc/server.bcfks"
    keyStoreType="BCFKS" keyStorePassword="a-14char-secret">
  <!-- existing app elements unchanged -->
</binding>

FIPS Support

The apache-activemq-artemis-fips Chainguard Container ships with a validated redistribution of the Bouncy Castle FIPS provider module. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Documentation and Resources

• Apache ActiveMQ Artemis official documentation
• Apache ActiveMQ Artemis Docker documentation
• Apache ActiveMQ Artemis GitHub repository
• ActiveMQ Artemis CLI reference
• BouncyCastle FIPS documentation

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.