Chainguard Container for nginx-s3-gateway-fips

NGINX S3 Gateway

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/nginx-s3-gateway-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 image is compatible with the upstream NGINX S3 Gateway image. Switching to Chainguard's image should not require any changes to your existing configuration.

By default, this image runs as a non-root user and listens on port 8080. For environments that require root privileges, root variants are available with the -root suffix (e.g., latest-root, latest-root-dev).

FIPS Support

The nginx-s3-gateway-fips Chainguard Image ships with a validated redistribution of the OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy

Getting Started

Docker

First, set up MinIO as an S3-compatible storage backend using Chainguard's MinIO image:

docker run -d \
  --name minio \
  -p 9000:9000 \
  -p 9001:9001 \
  -e MINIO_ROOT_USER=minioadmin \
  -e MINIO_ROOT_PASSWORD=minioadmin \
  cgr.dev/ORGANIZATION/minio server /data --console-address ":9001"

Create a bucket in MinIO:

docker exec minio mc alias set local http://localhost:9000 minioadmin minioadmin
docker exec minio mc mb local/mybucket

Now run NGINX S3 Gateway to proxy requests to MinIO:

docker run -d \
  --name nginx-s3-gateway-fips \
  -p 8080:8080 \
  -e S3_BUCKET_NAME=mybucket \
  -e S3_SERVER=host.docker.internal \
  -e S3_SERVER_PORT=9000 \
  -e S3_SERVER_PROTO=http \
  -e S3_STYLE=path \
  -e S3_REGION=us-east-1 \
  -e AWS_ACCESS_KEY_ID=minioadmin \
  -e AWS_SECRET_ACCESS_KEY=minioadmin \
  -e ALLOW_DIRECTORY_LIST=true \
  -e AWS_SIGS_VERSION=4 \
  cgr.dev/ORGANIZATION/nginx-s3-gateway-fips:latest

Test the gateway:

# Configure AWS CLI for MinIO
export AWS_ACCESS_KEY_ID=minioadmin
export AWS_SECRET_ACCESS_KEY=minioadmin

# Create and upload a file to MinIO
echo "Hello World" > test.txt
aws s3 cp test.txt s3://mybucket/ --endpoint-url http://localhost:9000

# Access the file through NGINX S3 Gateway
curl http://localhost:8080/test.txt

# List files through NGINX S3 Gateway
curl http://localhost:8080/

Kubernetes

For Kubernetes deployments, please refer to the upstream getting started guide which includes examples for various scenarios including EKS with IAM roles.

Documentation and Resources

• NGINX S3 Gateway Official Repository
• Getting Started Guide
• Environment Variables Reference
• Advanced Configuration

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.