Chainguard Container for secrets-store-csi-driver-provider-aws

The AWS provider for the Secrets Store CSI Driver allows you to fetch secrets from AWS Secrets Manager and AWS Systems Manager Parameter Store, and mount them into Kubernetes pods.

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/secrets-store-csi-driver-provider-aws:latest

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

Usage

The official docs provide a reference for setting up the AWS provider for Secrets Store CSI Driver. Below are some important considerations:

1. Using Chainguard Image:

   When installing the Secrets Store CSI Driver via Helm, you can utilize the secrets-store-csi-drive Chainguard image:

   helm repo add secrets-store-csi-driver https://kubernetes-sigs.github.io/secrets-store-csi-driver/charts
   helm install -n kube-system csi-secrets-store secrets-store-csi-driver/secrets-store-csi-driver \
     --set image.repository=cgr.dev/ORGANIZATION/secrets-store-csi-driver \
     --set image.tag=latest

2. Using Private ECR Repository:

   If you're using a private ECR repository, you will need the private-installer.yaml file, which can be found here. The private build section in the official docs has additional information for this setup.

   Follow the AWS ECR guide and pull the cgr.dev/ORGANIZATION/secrets-store-csi-driver image, tag it, and push it to your private repository($PRIVREPO).

3. FIPS Compliance:

   For FIPS-compliant images, set the FIPS endpoint in the Helm chart by adding the --set useFipsEndpoint=true flag during installation:

   helm repo add aws-secrets-manager https://aws.github.io/secrets-store-csi-driver-provider-aws
   helm install -n kube-system secrets-provider-aws aws-secrets-manager/secrets-store-csi-driver-provider-aws \
    --set image.repository=$PRIVREPO \
    --set image.tag=latest \
    --set useFipsEndpoint=true

   The $PRIVREPO here is your private ECR repository that contains the tagged cgr.dev/ORGANIZATION/secrets-store-csi-driver image.

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.