Chainguard Container for crossplane-aws-fips

FIPS-compliant Crossplane providers for managing Amazon Web Services (AWS) services on Kubernetes.

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/crossplane-aws-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 Crossplane AWS providers are comparable to the official AWS Crossplane providers with the following architectural differences:

• Deployment pattern: Deploy Chainguard's AWS family provider first, then deploy individual providers for services as needed.
• Package management: Chainguard's providers can not be installed with the Crossplane package manager.

Deployment

Upstream providers can be deployed individually and will automatically resolve their dependencies whereas Chainguard's providers require manual installation of dependencies. When deploying Chainguard's AWS Crossplane providers, skipDependencyResolution: true must be set in the resource for the provider you are deploying.

This is because the Crossplane package manifest used by Crossplane providers contain references to other dependencies, including the registry and repository of the dependency. Our customers use various repositories and registries and there isn't an effective way to account for all of them.

Because of this limitation, using the Crossplane package manager with these providers is not possible.

Getting Started

Deploy the AWS Family Provider

To manage resources on AWS with Crossplane, begin by deploying Chainguard's AWS family provider:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-family-aws
spec:
  package: cgr.dev/ORGANIZATION/crossplane-aws-fips:latest

Installing providers

Install the providers your deployment needs alongside the family provider. Use skipDependencyResolution: true to prevent upstream dependencies from being automatically installed:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-aws-s3
spec:
  package: cgr.dev/ORGANIZATION/crossplane-aws-s3-fips:latest
  skipDependencyResolution: true
---
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-aws-eks
spec:
  package: cgr.dev/ORGANIZATION/crossplane-aws-eks-fips:latest
  skipDependencyResolution: true

Configuration

After installing your desired providers, configure AWS credentials using a ProviderConfig:

# Create credentials secret
cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Secret
metadata:
  name: aws-secret
  namespace: crossplane-system
type: Opaque
stringData:
  creds: |
    [default]
    aws_access_key_id = ${AWS_ACCESS_KEY_ID}
    aws_secret_access_key = ${AWS_SECRET_ACCESS_KEY}
    aws_session_token = ${AWS_SESSION_TOKEN}
EOF

# Create ProviderConfig
cat <<EOF | kubectl apply -f -
apiVersion: aws.m.upbound.io/v1beta1
kind: ClusterProviderConfig
metadata:
  name: default
spec:
  credentials:
    source: Secret
    secretRef:
      namespace: crossplane-system
      name: aws-secret
      key: creds
EOF

Once configured, you can create AWS resources. Example S3 bucket creation:

apiVersion: s3.aws.m.upbound.io/v1beta1
kind: Bucket
metadata:
  name: my-secure-bucket
spec:
  forProvider:
    region: us-west-2
  providerConfigRef:
    name: default

Available Images

Documentation and Resources

• Crossplane AWS Provider Documentation
• Crossplane Getting Started Guide
• AWS Provider Examples

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.