Chainguard Container for amazon-cloudwatch-agent-operator

The Amazon CloudWatch Agent Operator is software developed to manage the CloudWatch Agent 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/amazon-cloudwatch-agent-operator:latest

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

Usage

For detailed instructions on the Amazon CloudWatch Agent Operator, refer to the official documentation. Ensure that you have appropriate permissions set up to allow CloudWatch to collect and send metrics and logs.

The source code and instructions for contributing to the operator can be found on GitHub.

Installation

There are several methods to install and configure the Amazon CloudWatch Agent Operator:

1. Using Helm Chart

To deploy the operator using Helm charts, you can use the following command. This command overrides the default image to use the Chainguard image

helm repo add aws-observability https://aws-observability.github.io/helm-charts
helm repo update aws-observability
helm install amazon-cloudwatch-agent-operator aws-observability/amazon-cloudwatch-observability \
  --create-namespace \
  --namespace amazon-cloudwatch-operator \
  --set clusterName=my-cluster-name \
  --set region=my-cluster-region \
  --set manager.image.repositoryDomainMap.public=cgr.dev/chainguard \
  --set manager.image.repository=amazon-cloudwatch-agent-operator \
  --set manager.image.tag=latest

Refer to the values.yaml file for more configuration options.

2. Using k8s Manifests

You can deploy cloudwatch agent and its operator using k8s manifests by following the steps outlined in the CloudWatch Setup Guide.

You can replace the default amazon-cloudwatch-agent-operator image with the Chainguard image by modifying the amazon-cloudwatch-observability-controller-manager deployment by replacing the manager image with the Chainguard image.

    spec:
      containers:
        command:
        - /manager
        image: cgr.dev/chainguard/amazon-cloudwatch-agent-operator:latest

3. GitHub Deployment

An easier way is setting up the deployment referring their GitHub, Running make deploy creates all the k8s resources.

git clone https://github.com/aws/amazon-cloudwatch-agent-operator.git
cd amazon-cloudwatch-agent-operator
make deploy

This command will create all necessary resources, and you can customize the deployment by modifying your CloudWatch configuration in resource definition. More details can be found in the repository README.

Additional Resources

• Amazon CloudWatch Documentation
• Helm Chart Documentation
• CloudWatch Agent Operator GitHub Repository

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.