THIS REPOSITORY IS NOW ARCHIVED IN FAVOR OF https://github.com/triggermesh/triggermesh
TriggerMesh Sources for Amazon Web Services (SAWS) allow you to quickly and easily consume events from your AWS services and send them to workloads running in your cluster.
Other Knative Sources maintained by TriggerMesh are available in the following repositories:
- Knative Sources
- GitLab Source (Knative sandbox project)
Using Helm:
$ helm repo add triggermesh https://storage.googleapis.com/triggermesh-charts
$ helm install triggermesh/aws-event-sources
Refer to the aws-event-sources chart documentation for all available configuration options.
Login to the OpenShift Container Platform console and install the AWS Sources Operator from the OperatorHub. Refer to the documentation of the AWS Event Sources Operator for the complete guide in getting up and running on the OpenShift Container Platform.
The following table lists the AWS services currently supported by TriggerMesh Sources for AWS and their support level.
AWS Service | Documentation | Support Level |
---|---|---|
CloudWatch | alpha | |
CloudWatch Logs | alpha | |
CodeCommit | README | alpha |
Cognito Identity Pool | README | alpha |
Cognito User Pool | README | alpha |
DynamoDB | README | alpha |
Kinesis | README | alpha |
Simple Cloud Storage (S3) | alpha | |
Simple Notifications Service (SNS) | README | alpha |
Simple Queue Service (SQS) | README | alpha |
For detailed usage instructions about a particular source, please refer to its linked README.md
file, or to the
TriggerMesh documentation.
We would love to hear your feedback on these sources. Please don't hesitate to submit bug reports and suggestions by filing issues, or contribute by submitting pull-requests.
Refer to DEVELOPMENT.md in order to get started.
TriggerMesh Sources for Amazon Web Services can be used as is from this repo. You can also use them along with other components from our Cloud at https://cloud.triggermesh.io, which has a web UI to configure and run them.
TriggerMesh Inc. supports those sources commercially. Email us at [email protected] to get more details.
Although this project is not part of the CNCF, we abide by its code of conduct.