​
DirectorySecurity Advisories
Sign In
Directory
amazon-cloudwatch-agent-operator logo

amazon-cloudwatch-agent-operator

Last changed

Sign In for Updates

Get notified of upcoming product changes, critical vulnerability notifications and patches and more.

Sign In
Versions
Overview
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Image for amazon-cloudwatch-agent-operator

The Amazon CloudWatch Agent Operator is software developed to manage the CloudWatch Agent on kubernetes.

Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.

Download this Image

This 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

Contact Support

If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.

What are Chainguard Images?

Chainguard Images are a collection of container images designed for security and minimalism.

Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.

The main features of Chainguard Images include:

-dev Variants

As mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev variant which does include a shell and package manager.

Although the -dev image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.

That being said, it’s worth noting that -dev variants of Chainguard Images are completely fine to run in production environments. After all, the -dev variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.

Learn More

To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.

Licenses

Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version 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

Category
application

Safe Source for Open Sourceâ„¢
Media KitContact Us
© 2024 Chainguard. All Rights Reserved.
Private PolicyTerms of Use

Product

Chainguard Images