AWS Kinesis Event Source
Features
Download this image
Description
Product EULA
The TriggerMesh End User License Agreement (EULA) for the AWS Kinesis event source is located in the event sources repository.
Instructions to obtain the container images from the hosted registry.
These images are also publicly available on the Google Container Registry (gcr.io/triggermesh/awskinesissource) and their sources are also publicly available on GitHub.
Use the following command(s) from a system with Docker service installed and running.
Examples:
The following two commands show you how to download the AWS Kinesis event source container from GCR and how to use it from the terminal or as a ContainerSource in Knative. Similar steps can be followed for each source with details available on GitHub.
$ docker pull registry.connect.redhat.com/triggermesh/awskinesissource
Quick Start commands to start the application
To use the AWS Kinesis as an example, in a terminal you can use the event source via the Docker CLI like so:
$ docker run --rm \
-e ARN=<arn_of_my_kinesis_stream> \
-e AWS_ACCESS_KEY_ID=<my_key_id> \
-e AWS_SECRET_ACCESS_KEY=<my_secret_key> \
-e NAME=my-awskinesissource \
-e NAMESPACE=default \
-e K_LOGGING_CONFIG='' \
-e K_METRICS_CONFIG='{"domain":"triggermesh.io/sources", "component":"awskinesissource", "configMap":{}}' \
registry.connect.redhat.com/triggermesh/awskinesissource:latest
In a Knative environment that supports the ContainerSource Kind you can copy the sample manifest from config/samples/awskinesis-containersource.yaml and replace the pre-filled environment variables under env with the values corresponding to your AWS Kinesis stream. Then, create that ContainerSource object in your Kubernetes cluster:
$ kubectl -n <my_namespace> create -f my-awskinesis-containersource.yaml
User Guide
The Triggermesh AWS Kinesis Event Source has a dedicated user guide available on the AWS event sources repository.
Support
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.
Products using this container
Image specifications
The following information was extracted from the dockerfile and other sources.
| Canonical image ID | AWS Kinesis Event Source |
| Summary | The TriggerMesh Kinesis 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. |
| Repository name | TriggerMesh AWS Kinesis Event Source |
| Image version | v1.10.0 |
| Architecture | amd64 |
Audit & compliance status
The following evidence verifies the image's security and build process compliance with mandated internal standards.
| Security audit date | 4/15/2024, 3:00:00 PM |
| Container certification |
Registry tokens
Use a registry service account token to authenticate your container client. This allows you to pull images without using your personal Red Hat credentials, which is recommended for CI/CD pipelines and automated deployments.
Using Podman login
Run the following command, then enter your registry token credentials when prompted by the terminal.
Pull the image
Image identifiers
Red Hat login
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
Using Podman login
Run the following command, then enter your login credentials when prompted by the terminal.
Pull the image
