AWS CloudWatch Logs source
Consumes logs from Amazon CloudWatch Logs.
apiVersion: sources.triggermesh.io/v1alpha1 kind: AWSCloudWatchLogsSource metadata: name: sample spec: arn: 'arn:aws:logs:us-west-2:123456789012:log-group:/aws/lambda/lambdadumper:*' pollingInterval: 5m auth: credentials: accessKeyID: valueFromSecret: name: awscreds key: aws_access_key_id secretAccessKey: valueFromSecret: name: awscreds key: aws_secret_access_key sink: ref: apiVersion: eventing.triggermesh.io/v1alpha1 kind: RedisBroker name: triggermesh
When TriggerMesh is running on Amazon EKS, you can use an IAM role for authentication rather than an access key and secret. In this case, TriggerMesh will generate a Kubernetes service account for you that will leverage this IAM role. You also have the option of specifying your own service account name, and if a service account with the same name already exists and it is already managed by the TriggerMesh controller, then it will be reused. By reusing the same serivce account in this way, you can avoid having to create many STS trust relationships for each generated service account.
For more details on authenticating with AWS, please take a look at our dedicated guide on AWS credentials. Events produced have the following attributes:
- Schema of the
See the Kubernetes object reference for more details.