aws-iam-controller-fips

packaged by Chainguard

Chainguard Container for aws-iam-controller-fips

FIPS-compliant IAM controller is an ACK service controller for AWS Identity and Access Management (IAM).

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-iam-controller-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-iam-controller-fips image is a lean, Wolfi-based container image. It is comparable to the IAM controller image published by AWS in functionality and has minimal dependencies, so it doesn't include a shell or package manager. The binary is exposed as /bin/controller (matching the upstream entrypoint and the path the upstream Helm chart's relative ./bin/controller command resolves to). This image runs as uid/gid 65532 (nonroot), unlike upstream's uid 1000; the ACK Helm chart sets runAsNonRoot but never pins a uid, so this is a safe deviation.

FIPS Support

This Chainguard container image ships with a validated redistribution of OpenSSL's FIPS provider module, and the controller binary performs its cryptographic operations through FIPS-validated modules. No configuration is required to enable FIPS mode. For more on FIPS support in Chainguard container images, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

The ACK (short for AWS Controllers for Kubernetes) service controller has a separate Helm chart that installs the necessary supporting artifacts as a Kubernetes deployment. This includes the ACK service controller, custom resource definitions (CRDs), and Kubernetes Role-Based Access Control (RBAC) manifests.

You can find Helm charts for ACK service controllers in the ACK registry within the Amazon ECR Public Gallery. Create a values.yaml pointing the IAM chart at this image:

image:
  repository: cgr.dev/ORGANIZATION/aws-iam-controller-fips
  tag: latest
aws:
  region: us-west-2

Then install the chart:

helm install --create-namespace -n ack-system ack-iam-controller \
  oci://public.ecr.aws/aws-controllers-k8s/iam-chart --values values.yaml

This installs the latest chart release; add --version to pin one of the published chart versions. Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

This Helm deployment will be fully functional once the ACK controllers have the required AWS IAM credentials to manage AWS resources. The ACK documentation includes resources on how to Configure IAM Permissions.

Documentation and Resources

Please refer to the AWS Controllers documentation for information on different ACK controllers and accessing different ACK resources.

You can explore the following resources to learn more about the IAM controller:

• AWS IAM Controller GitHub Project
• ACK controller deployment using Helm charts
• AWS Controllers documentation
• Working with resources with ACK controllers

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.