Chainguard Container for aws-sigv4-proxy

This project signs and proxies HTTP requests with Sigv4

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/aws-sigv4-proxy: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 Chainguard image is comparable to the upstream aws-observability/aws-sigv4-proxy image. Chainguard's container contains only the minimum set of dependencies needed to run aws-sigv4-proxy.

Getting Started

To get started with the aws-sigv4-proxy, you need to configure it with your AWS credentials and the target service you want to access. The proxy will sign requests using AWS Signature Version 4.

docker container run -d \
  --name aws-sigv4-proxy \
  -p 8080:8080 \
  -e AWS_ACCESS_KEY_ID="<YOUR_AWS_ACCESS_KEY_ID>" \
  -e AWS_SECRET_ACCESS_KEY="<YOUR_AWS_SECRET_ACCESS_KEY>" \
  cgr.dev/ORGANIZATION/aws-sigv4-proxy:latest

Then you can access the AWS service through the proxy by sending requests to http://localhost:8080. The proxy will automatically sign the requests with your AWS credentials.

For example to access an S3 bucket, you can use the following command:

# us-east-1
curl -s -H 'host: s3.amazonaws.com' http://localhost:8080/<BUCKET_NAME>

You will see the logs of the signing requests in the container logs, which will look like this:

2023/10/01 12:00:00 [INFO] Signing request for service s3 in region us-east-1
2023/10/01 12:00:00 [INFO] Request signed successfully
2023/10/01 12:00:00 [INFO] Forwarding request to s3.amazonaws.com

To learn more about how to run the aws-sigv4-proxy for different use cases, you can refer to the aws-sigv4-proxy examples in GitHub repository.

Also, you can deploy the aws-sigv4-proxy as a sidecar container alongside your application and there is a project named aws-sigv4-proxy-admission-controller that can automatically inject the aws-sigv4-proxy sidecar into your pods. To get more information about aws-sigv4-proxy-admission-controller, you can refer to the aws-sigv4-proxy-admission-controller GitHub repository.

Documentation and Resources

• AWS Signature Version 4 for API requests
• AWS SigV4 Proxy GitHub Repository

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.