s3proxy-fips

packaged by Chainguard

Chainguard Container for s3proxy-fips

S3Proxy allows applications to access other storage backends via the S3 API, with FIPS 140-3 validated cryptographic modules via Bouncy Castle FIPS.

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/s3proxy-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

The s3proxy-fips Chainguard Container is a FIPS-enabled variant of the s3proxy image. It is functionally identical to the standard s3proxy image, with the addition of FIPS 140-3 validated cryptographic modules via Bouncy Castle FIPS (BC-FIPS) for Java.

Key differences from the standard s3proxy image:

• Includes the openssl-config-fipshardened and openjdk-bcfips-policy-140-3-j21 packages for FIPS compliance.
• The JAVA_TOOL_OPTIONS environment variable is pre-configured to load the Bouncy Castle FIPS module.

Getting Started

To start s3proxy-fips with a local filesystem backend and anonymous access:

docker run -d --name s3proxy -p 8080:8080 \
  -e S3PROXY_AUTHORIZATION=none \
  cgr.dev/ORGANIZATION/s3proxy-fips:latest

Once the container is running, you can verify it is working by listing buckets:

curl http://localhost:8080/

To enable HTTPS with a BCFKS keystore (the FIPS-compliant keystore format):

# Generate a BCFKS keystore inside the FIPS container
docker run --rm -v $(pwd):/tls --entrypoint keytool \
  cgr.dev/ORGANIZATION/s3proxy-fips:latest \
  -genkeypair -alias s3proxy -keyalg RSA -keysize 2048 -validity 365 \
  -dname "CN=localhost" \
  -keystore /tls/keystore.bcfks -storetype BCFKS -providername BCFIPS \
  -storepass "YourPassword123!" -keypass "YourPassword123!"

# Start s3proxy with HTTPS
docker run -d --name s3proxy-tls -p 8443:8443 \
  -v $(pwd):/tls:ro \
  -e S3PROXY_AUTHORIZATION=none \
  -e S3PROXY_SECURE_ENDPOINT=https://0.0.0.0:8443 \
  -e S3PROXY_KEYSTORE_PATH=/tls/keystore.bcfks \
  -e S3PROXY_KEYSTORE_PASSWORD="YourPassword123!" \
  cgr.dev/ORGANIZATION/s3proxy-fips:latest

# Verify HTTPS endpoint
curl -k https://localhost:8443/

Configuration

For configuration options and environment variables, refer to the upstream S3Proxy documentation.

Documentation and Resources

• S3Proxy GitHub Repository
• Chainguard FIPS Containers Overview

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.