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.
