The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
The TriggerMesh End User License Agreement (EULA) for the AWS CloudWatch Logs event source is located in the event sources repository.
These images are also publicly available on the Google Container Registry (gcr.io/triggermesh/awscloudwatchlogssource and their sources are also publicly available on GitHub.
$ docker pull registry.connect.redhat.com/triggermesh/awscloudwatchlogssource
In a Knative environment you can copy the sample manifest from config/samples/awscloudwatchlogssource.yaml and replace the pre-filled environment variables under env with the values corresponding to your AWS CloudWatch Logs. Then, create the Source object in your Kubernetes cluster:
$ kubectl -n <my_namespace> create -f awscloudwatchlogssource.yaml
The Triggermesh AWS CloudWatch Event Source has a dedicated user guide available on the AWS event sources repository.
TriggerMesh Inc. supports the event sources commercially, email info@triggermesh.com to get more details.
For best effort community support do not hesitate to let us know what is wrong and how we could improve them, just file an issue or join those of use who are maintaining them and submit a pull request on GitHub.
The following information was extracted from the containerfile and other sources.
Summary | The TriggerMesh CloudWatch Log Source |
Description | The Universal Base Image Minimal is a stripped down image that uses microdnf as a package manager. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly. |
Provider | TriggerMesh |
Maintainer | Red Hat, Inc. |
The following information was extracted from the containerfile and other sources.
Repository name | TriggerMesh AWS CloudWatch Log Event Source |
Image version | v1.10.0 |
Architecture | amd64 |
Use the following instructions to get images from a Red Hat container registry using registry service account tokens. You will need to create a registry service account to use prior to completing any of the following tasks.
First, you will need to add a reference to the appropriate secret and repository to your Kubernetes pod configuration via an imagePullSecrets field.
Then, use the following from the command line or from the OpenShift Dashboard GUI interface.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running