AWS Kinesis Firehose
Since Camel 3.2
Only producer is supported
The AWS2 Kinesis Firehose component supports sending messages to Amazon Kinesis Firehose service (Batch not supported).
Prerequisites
You must have a valid Amazon Web Services developer account, and be signed up to use Amazon Kinesis Firehose. More information are available at AWS Kinesis Firehose
The AWS2 Kinesis Firehose component is not supported in OSGI |
URI Format
aws2-kinesis-firehose://delivery-stream-name[?options]
The stream needs to be created prior to it being used.
You can append query options to the URI in the following format, ?options=value&option2=value&…
Configuring Options
Camel components are configured on two separate levels:
-
component level
-
endpoint level
Configuring Component Options
The component level is the highest level which holds general and common configurations that are inherited by the endpoints. For example a component may have security settings, credentials for authentication, urls for network connection and so forth.
Some components only have a few options, and others may have many. Because components typically have pre configured defaults that are commonly used, then you may often only need to configure a few options on a component; or none at all.
Configuring components can be done with the Component DSL, in a configuration file (application.properties|yaml), or directly with Java code.
Configuring Endpoint Options
Where you find yourself configuring the most is on endpoints, as endpoints often have many options, which allows you to configure what you need the endpoint to do. The options are also categorized into whether the endpoint is used as consumer (from) or as a producer (to), or used for both.
Configuring endpoints is most often done directly in the endpoint URI as path and query parameters. You can also use the Endpoint DSL and DataFormat DSL as a type safe way of configuring endpoints and data formats in Java.
A good practice when configuring options is to use Property Placeholders, which allows to not hardcode urls, port numbers, sensitive information, and other settings. In other words placeholders allows to externalize the configuration from your code, and gives more flexibility and reuse.
The following two sections lists all the options, firstly for the component followed by the endpoint.
Component Options
The AWS Kinesis Firehose component supports 18 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
This option will set the CBOR_ENABLED property during the execution. | true | boolean | |
Component configuration. | KinesisFirehose2Configuration | ||
Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option. | false | boolean | |
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. | String | ||
Set whether the Kinesis Firehose client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | boolean | |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | boolean | |
The operation to do in case the user don’t want to send only a record. Enum values:
| KinesisFirehose2Operations | ||
The region in which Kinesis Firehose client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You’ll need to use the name Region.EU_WEST_1.id(). | String | ||
Autowired Amazon Kinesis Firehose client to use for all requests for this endpoint. | FirehoseClient | ||
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | boolean | |
To define a proxy host when instantiating the Kinesis Firehose client. | String | ||
To define a proxy port when instantiating the Kinesis Firehose client. | Integer | ||
To define a proxy protocol when instantiating the Kinesis Firehose client. Enum values:
| HTTPS | Protocol | |
Amazon AWS Access Key. | String | ||
If using a profile credentials provider this parameter will set the profile name. | String | ||
Amazon AWS Secret Key. | String | ||
If we want to trust all certificates in case of overriding the endpoint. | false | boolean | |
Set whether the Kinesis Firehose client should expect to load credentials through a profile credentials provider. | false | boolean |
Endpoint Options
The AWS Kinesis Firehose endpoint is configured using URI syntax:
aws2-kinesis-firehose:streamName
with the following path and query parameters:
Query Parameters (16 parameters)
Name | Description | Default | Type |
---|---|---|---|
This option will set the CBOR_ENABLED property during the execution. | true | boolean | |
Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option. | false | boolean | |
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. | String | ||
The operation to do in case the user don’t want to send only a record. Enum values:
| KinesisFirehose2Operations | ||
The region in which Kinesis Firehose client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You’ll need to use the name Region.EU_WEST_1.id(). | String | ||
Set whether the Kinesis Firehose client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | boolean | |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | boolean | |
Autowired Amazon Kinesis Firehose client to use for all requests for this endpoint. | FirehoseClient | ||
To define a proxy host when instantiating the Kinesis Firehose client. | String | ||
To define a proxy port when instantiating the Kinesis Firehose client. | Integer | ||
To define a proxy protocol when instantiating the Kinesis Firehose client. Enum values:
| HTTPS | Protocol | |
Amazon AWS Access Key. | String | ||
If using a profile credentials provider this parameter will set the profile name. | String | ||
Amazon AWS Secret Key. | String | ||
If we want to trust all certificates in case of overriding the endpoint. | false | boolean | |
Set whether the Kinesis Firehose client should expect to load credentials through a profile credentials provider. | false | boolean |
Required Kinesis Firehose component options
You have to provide the FirehoseClient in the Registry with proxies and relevant credentials configured.
Usage
Static credentials, Default Credential Provider and Profile Credentials Provider
You have the possibility of avoiding the usage of 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.accessKeyId and aws.secretKey
-
Environment variables - AWS_ACCESS_KEY_ID and AWS_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_URI is set.
-
Amazon EC2 Instance profile credentials.
You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of static, default and profile credentials could be used at the same time.
For more information about this you can look at AWS credentials documentation
Message Headers
The AWS Kinesis Firehose component supports 3 message header(s), which is/are listed below:
Name | Description | Default | Type |
---|---|---|---|
CamelAwsKinesisFirehoseRecordId (producer) Constant: | The record ID, as defined in http://docs.aws.amazon.com/firehose/latest/APIReference/API_PutRecord.html#API_PutRecord_ResponseSyntaxResponse Syntax. | String | |
CamelAwsKinesisFirehoseOperation (producer) Constant: | The operation we want to perform. | String | |
CamelAwsKinesisFirehoseDeliveryStreamName (producer) Constant: | The name of the delivery stream. | String |
Amazon Kinesis Firehose configuration
You then have to reference the FirehoseClient in the amazonKinesisFirehoseClient
URI option.
from("aws2-kinesis-firehose://mykinesisdeliverystream?amazonKinesisFirehoseClient=#kinesisClient")
.to("log:out?showAll=true");
Providing AWS Credentials
It is recommended that the credentials are obtained by using the DefaultAWSCredentialsProviderChain that is the default when creating a new ClientConfiguration instance, however, a different AWSCredentialsProvider can be specified when calling createClient(…).
Kinesis Firehose Producer operations
Camel-AWS s3 component provides the following operation on the producer side:
-
SendBatchRecord
-
CreateDeliveryStream
-
DeleteDeliveryStream
-
DescribeDeliveryStream
-
UpdateDestination
Send Batch Records Example
You can send an iterable of Kinesis Record (as the following example shows) or you can send directly a PutRecordBatchRequest POJO instance in the body.
@Test
public void testFirehoseBatchRouting() throws Exception {
Exchange exchange = template.send("direct:start", ExchangePattern.InOnly, new Processor() {
public void process(Exchange exchange) throws Exception {
List<Record> recs = new ArrayList<Record>();
Record rec = Record.builder().data(SdkBytes.fromString("Test1", Charset.defaultCharset())).build();
Record rec1 = Record.builder().data(SdkBytes.fromString("Test2", Charset.defaultCharset())).build();
recs.add(rec);
recs.add(rec1);
exchange.getIn().setBody(recs);
}
});
assertNotNull(exchange.getIn().getBody());
}
from("direct:start").to("aws2-kinesis-firehose://cc?amazonKinesisFirehoseClient=#FirehoseClient&operation=sendBatchRecord");
In the deliveryStream you’ll find "Test1Test2".
Dependencies
Maven users will need to add the following dependency to their pom.xml.
pom.xml
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-aws2-kinesis</artifactId>
<version>${camel-version}</version>
</dependency>
where ${camel-version}
must be replaced by the actual version of Camel.
Spring Boot Auto-Configuration
When using aws2-kinesis-firehose with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-aws2-kinesis-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
The component supports 46 options, which are listed below.