Chainguard Container for elasticsearch-fips

Elasticsearch is a distributed search and analytics engine, scalable data store and vector database optimized for speed and relevance on production-scale workloads.

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/elasticsearch-fips:latest

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

FIPS Notes

This build of Elasticsearch was modified to support Chainguard FIPS Java with FIPS 140-3 support.

Chainguard FIPS Java with FIPS 140-3 is based on validated BouncyCastle FIPS 2.1 with hardware-accelerated cryptography and a user-space entropy source.

The following modifications were applied to the Elasticsearch codebase:

• Upgrade internal entitlements to grant permissions for BC-FIPS 2.1 provider to operate
• Upgrade internal entitlements to grant permissions for BC-RNG-JENT provider to operate
• Fix internal entitlements to access default cacerts trust store certficated
• Fix internal entitlements to access default jssecacerts trust store certficated
• Fix internal entitlements to correctly read BC-FIPS approved_only mode setting via either system or security properties
• Fix internal entitlements to grant watcher access to bc-mail.
• Implement autodetection support for BCFKS keystore format (required by BC-FIPS)
• Remove FIPS unapproved TLS ciphers from default TLS config
• Remove Java obsoleted TLS ciphers from default TLS config
• Set FIPS mode to enabled by default
• Set FIPS required providers to BCFIPS, BCJSSE, BCRNG
• Set default keystore format to BCFKS by default
• Port certificate creation and autoconfiguration to use BCFKS by default
• Correctly use FIPS bouncycastle, instead of non-fips bouncy castle for encryption/decryption of certificates
• Update entrypoint to use a stock password of "changeitchangeit" (instead of empty) for the elasticsearch-keystore which is used to store passwords for the key and trust stores.

With the above changes this images achieves FIPS 140-3 compliance powered by Chainguard FIPS Java.

Automatic trust-store & keystore configuration works as well, as all the commands are updated to use BCFKS keystore format by default. One can use auto-configuration or the elasticsearch-certutil from this image to create compliant keystore. Alternative is to export existing keys and certificates, and reimport them into a keystore created with keyutil from this image. If you need additional help with certificates generation, import/export, please open a support request.

This image is tested to launch elasticsearch with docker run, as well as helm chart deployments with an ECK operator upon every image release.

Elastic license is required to use this image!

To run Elasticsearch in FIPS mode, you will need to provide a license key. To obtain a license for Elasticsearch, see their subscriptions page here.

Chainguard recommends Platinum license.

Adding plugins to the image

Elasticsearch provides a mechanism to add plugins to the image. This process is outlined in the Elasticsearch ECK documentation.

Unlike the upstream Elasticsearch image, we provide all Elasticsearch utilities in the local path so that they can be ran directly. Due to this, we do not need to prefix bin/ to the executable path for elasticsearch-plugin, and we can just invoke it directly. Here's an example installing the analysis-icu plugin:

FROM cgr.dev/ORGANIZATION/elasticsearch-fips:latest
RUN elasticsearch-plugin install --batch analysis-icu

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.