이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 8. AWS Kinesis Source
Receive data from AWS Kinesis.
8.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
8.2. Usage example with plain consumer 링크 복사링크가 클립보드에 복사되었습니다!
You could consume the stream content directly
- route:
from:
uri: "kamelet:aws-kinesis-source"
parameters:
useDefaultCredentialsProvider: true
region: "eu-west-1"
stream: "kamelets"
steps:
- to:
uri: "kamelet:log-sink"
8.3. Usage example with KCL Consumer 링크 복사링크가 클립보드에 복사되었습니다!
You could consume the stream content with the KCL support
- route:
from:
uri: "kamelet:aws-kinesis-source"
parameters:
stream: "kamelets"
useDefaultCredentialsProvider: true
region: "eu-west-1"
asyncClient: true
useKclConsumers: true
steps:
- to:
uri: "kamelet:log-sink"
parameters:
showHeaders: true
With the useKclConsumers enabled, you won’t have to deal with shard iteration directly. Everything is managed by the AWS Kinesis client library and the KCL layer.
As a side note you need to remember that the KCL consumer will need access to DynamoDB and Cloudwatch services from AWS, so it will create clients to these services under the hood and it will use them.
8.4. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the aws-kinesis-source Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| region * | AWS Region | The AWS region to access. | string | ||
| stream * | Stream Name | The Kinesis stream that you want to access. The Kinesis stream that you specify must already exist. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | string | ||
| asyncClient | Async Client | If we want a KinesisAsyncClient instance set it to true. | boolean | False | |
| delay | Delay | The number of milliseconds before the next poll of the selected stream. | integer | 500 | |
| kclDisableCloudwatchMetricsExport | KCL Disable Cloudwatch Metrics Export | Define if we want to use a KCL Consumer and disable the CloudWatch Metrics Export | boolean | False | |
| overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
| useDefaultCredentialsProvider | Default Credentials Provider | If true, the Kinesis client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key). | boolean | False | |
| useKclConsumers | KCL Consumer | If we want to a KCL Consumer set it to true | boolean | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the Kinesis client should expect to load credentials through a profile credentials provider. | boolean | False | |
| useSessionCredentials | Session Credentials | Set whether the Kinesis client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in Kinesis. | boolean | False |
* = Fields marked with an asterisk are mandatory.
8.5. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
8.5.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
<dependencies>
<dependency>
<groupId>org.apache.camel.kamelets</groupId>
<artifactId>camel-kamelets-utils</artifactId>
<version>4.8.5</version>
</dependency>
<dependency>
<groupId>org.apache.camel.quarkus</groupId>
<artifactId>camel-quarkus-aws-kinesis-source</artifactId>
</dependency>
<dependency>
<groupId>org.apache.camel.quarkus</groupId>
<artifactId>camel-quarkus-aws2-kinesis</artifactId>
</dependency>
<dependency>
<groupId>org.apache.camel.quarkus</groupId>
<artifactId>camel-quarkus-kamelet</artifactId>
</dependency>
</dependencies>
8.6. Usage 링크 복사링크가 클립보드에 복사되었습니다!
8.6.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
8.6.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
8.6.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
- route:
from:
uri: "kamelet:timer-source"
parameters:
period: 10000
message: 'test'
steps:
- to:
uri: "kamelet:log-sink"
You can now run it directly through the following command.
camel run route.yaml
8.6.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-kinesis-source Kamelet as a Knative source by binding it to a Knative object.
aws-kinesis-source-binding.yaml
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
name: aws-kinesis-source-binding
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: aws-kinesis-source
properties:
accessKey: "The Access Key"
region: "eu-west-1"
secretKey: "The Secret Key"
stream: "The Stream Name"
sink:
ref:
kind: Channel
apiVersion: messaging.knative.dev/v1
name: mychannel
8.6.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-kinesis-source Kamelet as a Kafka source by binding it to a Kafka topic.
aws-kinesis-source-binding.yaml
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
name: aws-kinesis-source-binding
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: aws-kinesis-source
properties:
accessKey: "The Access Key"
region: "eu-west-1"
secretKey: "The Secret Key"
stream: "The Stream Name"
sink:
ref:
kind: KafkaTopic
apiVersion: kafka.strimzi.io/v1beta1
name: my-topic