Last changed
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Request trialKubernetes Cluster API Provider AWS provides consistent deployment and day 2 operations of "self-managed" and EKS Kubernetes clusters on AWS
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard Registry.
Chainguard's cluster-api-aws-controller image is compatible with the upstream Cluster API Provider AWS. This image contains only the minimum set of dependencies needed to run the AWS infrastructure provider components.
The Cluster API Provider for AWS enables you to create and manage Kubernetes clusters on Amazon Web Services using Cluster API. It provides declarative APIs for provisioning and managing AWS infrastructure resources including EC2 instances, VPCs, load balancers, and security groups.
clusterctl
CLI toolInitialize the AWS infrastructure provider using clusterctl:
Or manually install using the Chainguard image by applying the InfrastructureProvider resource:
Create an AWS cluster using Cluster API resources:
The controller requires AWS credentials with the following IAM permissions:
Create and configure the credentials secret:
Where aws-credentials
file contains:
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:
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.
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.
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.
Chainguard container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
Apache-2.0
LGPL-2.1-or-later
MIT
MPL-2.0
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementA FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.