/
DirectorySecurity AdvisoriesPricing
Sign inRequest a trial
Directory
crossplane-aws-kinesis logo

crossplane-aws-kinesis

Last changed

Request a free trial

Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.

Request trial
Tags
Overview
Comparison
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Container for crossplane-aws

Crossplane provider for managing Amazon Web Services (AWS) config services in 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: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 upstream AWS providers with the following architectural differences:

  • Upstream providers can be deployed independently and automatically resolve their dependencies
  • Chainguard providers require manual installation of the family provider and use skipDependencyResolution: true for component providers to prevent automatic upstream dependency resolution
  • Deployment pattern: Install the Chainguard family provider first, then add individual component providers as needed
  • Functionality: Provides equivalent AWS resource management capabilities with this modified deployment approach

Getting Started

Using the AWS Family Provider

For comprehensive AWS resource management, install the family provider that includes all AWS services:

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

Using Individual Component Providers

For targeted deployments, install specific component providers alongside the family provider. Use skipDependencyResolution: true to prevent automatic upstream family provider installation:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-aws-s3
spec:
  package: cgr.dev/ORGANIZATION/crossplane-aws-s3:latest
  skipDependencyResolution: true
---
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-aws-eks
spec:
  package: cgr.dev/ORGANIZATION/crossplane-aws-eks: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

Upstream ImageChainguard Image

xpkg.upbound.io/upbound/provider-family-aws

cgr.dev/ORGANIZATION/crossplane-aws

xpkg.upbound.io/upbound/provider-aws-cloudfront

cgr.dev/ORGANIZATION/crossplane-aws-cloudfront

xpkg.upbound.io/upbound/provider-aws-cloudwatchlogs

cgr.dev/ORGANIZATION/crossplane-aws-cloudwatchlogs

xpkg.upbound.io/upbound/provider-aws-dynamodb

cgr.dev/ORGANIZATION/crossplane-aws-dynamodb

xpkg.upbound.io/upbound/provider-aws-ec2

cgr.dev/ORGANIZATION/crossplane-aws-ec2

xpkg.upbound.io/upbound/provider-aws-eks

cgr.dev/ORGANIZATION/crossplane-aws-eks

xpkg.upbound.io/upbound/provider-aws-firehose

cgr.dev/ORGANIZATION/crossplane-aws-firehose

xpkg.upbound.io/upbound/provider-aws-iam

cgr.dev/ORGANIZATION/crossplane-aws-iam

xpkg.upbound.io/upbound/provider-aws-kinesis

cgr.dev/ORGANIZATION/crossplane-aws-kinesis

xpkg.upbound.io/upbound/provider-aws-kms

cgr.dev/ORGANIZATION/crossplane-aws-kms

xpkg.upbound.io/upbound/provider-aws-lambda

cgr.dev/ORGANIZATION/crossplane-aws-lambda

xpkg.upbound.io/upbound/provider-aws-rds

cgr.dev/ORGANIZATION/crossplane-aws-rds

xpkg.upbound.io/upbound/provider-aws-s3

cgr.dev/ORGANIZATION/crossplane-aws-s3

xpkg.upbound.io/upbound/provider-aws-sns

cgr.dev/ORGANIZATION/crossplane-aws-sns

xpkg.upbound.io/upbound/provider-aws-sqs

cgr.dev/ORGANIZATION/crossplane-aws-sqs

Documentation and Resources

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:

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.

Licenses

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 agreement

Compliance

A FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.


Related images
crossplane-aws-kinesis-fips logoFIPS
crossplane-aws-kinesis-fips

Category
application

Safe Source for Open Source™
Contact us
© 2025 Chainguard. All Rights Reserved.
Private PolicyTerms of Use

Products

Chainguard ContainersChainguard LibrariesChainguard VMs