Amazon Kinesis source
apiVersion: sources.triggermesh.io/v1alpha1 kind: AWSKinesisSource metadata: name: sample spec: arn: arn:aws:kinesis:us-west-2:123456789012:stream/triggermeshtest 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
Alternatively you can use an IAM role for authentication instead of an access key and secret, for Amazon EKS only:
To setup an IAM role for service accounts, please refer to the official AWS documentation.
Events produced have the following attributes:
- Schema of the
See the Kubernetes object reference for more details.
- Kinesis Data Stream
- Amazon Resource Name (ARN)
- API Credentials
Kinesis Data Stream
If you don't already have an Amazon Kinesis Data Stream, create one by following the instructions at Creating and Updating Data Streams.
Amazon Resource Name (ARN)
A fully qualified ARN is required to uniquely identify the Amazon Kinesis Stream.
This ARN can be obtained directly from the overview page of the Kinesis Stream. It typically has the following format:
Alternatively, one can obtain the ARN of a Kinesis Stream by using the AWS CLI. The following command
retrieves the information of a stream called
triggermeshtest in the
The TriggerMesh event source for Amazon Kinesis authenticates calls to the AWS API using AWS Access Keys. The page Understanding and getting your AWS credentials contains instructions to create access keys when signed-in either as the root user or as an IAM user. Take note of the Access Key ID and Secret Access Key, they will be used to create an instance of the event source.
It is considered a good practice to create dedicated users with restricted privileges in order to programmatically access AWS services. Permissions can be added or revoked granularly for a given IAM user by attaching IAM Policies to it.
As an example, the following policy contains only the permissions required by the TriggerMesh Amazon Kinesis event source to operate: