AWS SNS Event Source
Description
Product EULA
The TriggerMesh End User License Agreement (EULA) for the AWS SNS 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/awssnssource) 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 SNS 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/awssnssource
Quick Start commands to start the application
To use the AWS SNS 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_sns_topic> \
-e PUBLIC_URL=<public_source_url> \
-e AWS_ACCESS_KEY_ID=<my_key_id> \
-e AWS_SECRET_ACCESS_KEY=<my_secret_key> \
-e NAME=my-awssnssource \
-e NAMESPACE=default \
-e K_LOGGING_CONFIG='' \
-e K_METRICS_CONFIG='{"domain":"triggermesh.io/sources", "component":"awssnssource", "configMap":{}}' \
registry.connect.redhat.com/triggermesh/awssnssource:latest
In a Knative environment that supports the ContainerSource Kind you can copy the sample manifest from config/samples/awssns-containersource.yaml and replace the pre-filled environment variables under env with the values corresponding to your AWS SNS topic. Then, create that ContainerSource object in your Kubernetes cluster:
$ kubectl -n <my_namespace> create -f my-awssns-containersource.yaml
User Guide
The Triggermesh AWS SNS 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
General information
The following information was extracted from the containerfile and other sources.
| Summary | The TriggerMesh SNS 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. |
Technical information
The following information was extracted from the containerfile and other sources.
| Repository name | TriggerMesh AWS SNS 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.
Using OpenShift secrets
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.
Using podman login
Use the following command(s) from a system with podman installed
Using docker login
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.
Using OpenShift
For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.
Using podman login
Use the following command(s) from a system with podman installed
Using docker login
Use the following command(s) from a system with docker service installed and running
