Chainguard Container for aws-efs-csi-driver-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/aws-efs-csi-driver-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

Chainguard's AWS Elastic File System (EFS) Container Storage Interface (CSI) driver image is comparable to the amazon/aws-efs-csi-driver image on Docker Hub. As with many of Chainguard's other container images, the AWS EFS CSI driver image contains only the minimum number of dependencies it needs to function. This means it doesn't include things like a shell or package manager.

FIPS support

The aws-efs-csi-driver-fips Chainguard Image ships with a validated redistribution of the OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Images, consult our guide on FIPS-enabled Chainguard Images on Chainguard Academy

Getting Started

The EFS CSI driver requires IAM permissions to interact with your filesystem. This includes an IAM role and policies, as well as a service account and annotation to assume the role.

Refer to the AWS documentations resources on creating an IAM role for more information.

Install with Helm

For complete instructions on installing this image with Helm, please refer to the Helm chart documentation.

The following is an example of how to use the Helm chart, using the Chainguard image. This example enables the useFips argument, which will instruct the EFS CSI driver to use the FIPS service endpoint for AWS EFS.

Start by adding a values.yaml file to configure the Helm chart:

cat <<EOF > values.yaml
image:
  repository: cgr.dev/ORGANIZATION/aws-efs-csi-driver-fips
  tag: latest
  digest: null
controller:
  serviceAccount:
  create: false
  name: efs-csi-controller-sa
useFips: true
EOF

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

Add the Helm repository:

helm repo add aws-efs-csi-driver https://kubernetes-sigs.github.io/aws-efs-csi-driver/
helm repo update

Then Install the chart:

helm upgrade --install aws-efs-csi-driver --namespace kube-system aws-efs-csi-driver/aws-efs-csi-driver -f values.yaml

Install as an EKS add-on

Amazon's Elastic Kubernetes Service (EKS) allows you to install the efs-csi-driver as an EKS add-on. For complete instructions on how you can do this, refer to the upstream documentation.

If you've chosen this installation method, there are two caveats to be aware of:

1. You cannot specify a custom image while installing as an EKS add-on
2. You cannot specify the useFips argument to force the EFS CSI to use FIPS endpoints

You'll need to patch the efs-csi-controller deployment to use the Chainguard image, and this is a step you'll need to repeat each time that you re-deploy or upgrade the version using EKS add-ons.

Additionally, you'll need to patch the DaemonSets to set AWS_USE_FIPS_ENDPOINT=true.

Documentation and Resources

For more information, please refer to the upstream documentation.

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.