aws-sigv4-proxy-fips

Fips

Infra

Stig

Updated 4 days ago

AWS-SigV4-Proxy-FIPS Overview

Secure your stack with a hardened AWS-SigV4-Proxy-FIPS image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.

AWS SigV4 Proxy is a lightweight proxy server that automatically handles authentication for AWS services. It is often deployed as a Kubernetes sidecar to connect open-source software that doesn't natively support AWS auth to AWS managed services.

FIPS 140-3 Certification

This image is FIPS-validated to ensure its cryptographic operations meet the Federal Information Processing Standards (FIPS) required for secure government and regulated environments. Its core cryptographic modules are validated under the NIST Cryptographic Module Validation Program (CMVP) and comply with the FIPS 140-3 standard.

To verify that the FIPS 140-3 provider is configured and active, follow the instructions in the FIPS compliance tab.

Try It Out

For a quick test, start the AWS SigV4 Proxy container locally with your AWS profile so the proxy can sign any AWS requests sent through it:

docker run --rm -ti \
  --name aws-sigv4-proxy \
  -v ~/.aws:/root/.aws:ro \
  -p 8080:8080 \
  -e AWS_SDK_LOAD_CONFIG=true \
  -e AWS_PROFILE={profile} \
  reg.mini.dev/aws-sigv4-proxy-fips \
  -v

The command exposes the proxy on port 8080, and runs the proxy in the foreground so you can see the verbose logs. Replace {profile} with the name of the AWS profile you want to use from ~/.aws.

Next, send a test request to S3 through the proxy (first update it with your AWS resource details):

curl -v \
  -H "Host: my-bucket.s3.us-east-1.amazonaws.com" \
  "http://localhost:8080/my-folder/test.txt"

Technical Considerations

The AWS-SigV4-Proxy-FIPS image provided by Minimus is a slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.

AWS-SigV4-Proxy-FIPS built by Minimus:

Runs as non-root by default for a security-first approach that protects against privilege escalation attacks.
Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.