AWS 2 Managed Streaming for Apache Kafka (MSK)
Since Camel 3.1
Only producer is supported
The AWS2 MSK component supports create, run, start, stop and terminate AWS MSK instances.
Prerequisites
You must have a valid Amazon Web Services developer account, and be signed up to use Amazon MSK. More information is available at Amazon MSK.
The AWS2 MSK component is not supported in OSGI |
URI Format
aws2-msk://label[?options]
You can append query options to the URI in the following format, ?options=value&option2=value&…
URI Options
The AWS 2 Managed Streaming for Apache Kafka (MSK) component supports 13 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
configuration (producer) |
Component configuration |
MSK2Configuration |
|
lazyStartProducer (producer) |
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 |
mskClient (producer) |
Autowired To use a existing configured AWS MSK as client |
KafkaClient |
|
operation (producer) |
Required The operation to perform. There are 4 enums and the value can be one of: listClusters, createCluster, deleteCluster, describeCluster |
MSK2Operations |
|
pojoRequest (producer) |
If we want to use a POJO request as body or not |
false |
boolean |
proxyHost (producer) |
To define a proxy host when instantiating the MSK client |
String |
|
proxyPort (producer) |
To define a proxy port when instantiating the MSK client |
Integer |
|
proxyProtocol (producer) |
To define a proxy protocol when instantiating the MSK client. There are 2 enums and the value can be one of: HTTP, HTTPS |
HTTPS |
Protocol |
region (producer) |
The region in which MSK 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 |
|
trustAllCertificates (producer) |
If we want to trust all certificates in case of overriding the endpoint |
false |
boolean |
autowiredEnabled (advanced) |
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 |
accessKey (security) |
Amazon AWS Access Key |
String |
|
secretKey (security) |
Amazon AWS Secret Key |
String |
The AWS 2 Managed Streaming for Apache Kafka (MSK) endpoint is configured using URI syntax:
aws2-msk:label
with the following path and query parameters:
Query Parameters (12 parameters):
Name | Description | Default | Type |
---|---|---|---|
lazyStartProducer (producer) |
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 |
mskClient (producer) |
Autowired To use a existing configured AWS MSK as client |
KafkaClient |
|
operation (producer) |
Required The operation to perform. There are 4 enums and the value can be one of: listClusters, createCluster, deleteCluster, describeCluster |
MSK2Operations |
|
pojoRequest (producer) |
If we want to use a POJO request as body or not |
false |
boolean |
proxyHost (producer) |
To define a proxy host when instantiating the MSK client |
String |
|
proxyPort (producer) |
To define a proxy port when instantiating the MSK client |
Integer |
|
proxyProtocol (producer) |
To define a proxy protocol when instantiating the MSK client. There are 2 enums and the value can be one of: HTTP, HTTPS |
HTTPS |
Protocol |
region (producer) |
The region in which MSK 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 |
|
trustAllCertificates (producer) |
If we want to trust all certificates in case of overriding the endpoint |
false |
boolean |
synchronous (advanced) |
Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). |
false |
boolean |
accessKey (security) |
Amazon AWS Access Key |
String |
|
secretKey (security) |
Amazon AWS Secret Key |
String |
Required MSK component options
You have to provide the amazonMskClient in the Registry or your accessKey and secretKey to access the Amazon MSK service.
Usage
Message headers evaluated by the MSK producer
Header | Type | Description |
---|---|---|
|
|
The operation to perform |
|
|
The cluster name filter for list operation |
|
|
The cluster name for list and create operation |
|
|
The cluster arn for delete operation |
|
|
The Kafka for the cluster during create operation |
|
|
The number of nodes for the cluster during create operation |
|
|
The Broker nodes group info to provide during the create operation |
Producer Examples
-
listClusters: this operation will list the available MSK Brokers in AWS
from("direct:listClusters")
.to("aws2-msk://test?mskClient=#amazonMskClient&operation=listClusters")
-
createCluster: this operation will create an MSK Cluster in AWS
from("direct:createCluster")
.process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(MSK2Constants.CLUSTER_NAME, "test-kafka");
exchange.getIn().setHeader(MSK2Constants.CLUSTER_KAFKA_VERSION, "2.1.1");
exchange.getIn().setHeader(MSK2Constants.BROKER_NODES_NUMBER, 2);
BrokerNodeGroupInfo groupInfo = BrokerNodeGroupInfo.builder().build();
exchange.getIn().setHeader(MSK2Constants.BROKER_NODES_GROUP_INFO, groupInfo);
}
})
.to("aws2-msk://test?mskClient=#amazonMskClient&operation=createCluster")
-
deleteCluster: this operation will delete an MSK Cluster in AWS
from("direct:deleteCluster")
.setHeader(MSK2Constants.CLUSTER_ARN, constant("test-kafka"));
.to("aws2-msk://test?mskClient=#amazonMskClient&operation=deleteCluster")
from("direct:createCluster")
.process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(MSK2Constants.CLUSTER_NAME, "test-kafka");
exchange.getIn().setHeader(MSK2Constants.CLUSTER_KAFKA_VERSION, "2.1.1");
exchange.getIn().setHeader(MSK2Constants.BROKER_NODES_NUMBER, 2);
BrokerNodeGroupInfo groupInfo = BrokerNodeGroupInfo.builder().build();
exchange.getIn().setHeader(MSK2Constants.BROKER_NODES_GROUP_INFO, groupInfo);
}
})
.to("aws2-msk://test?mskClient=#amazonMskClient&operation=deleteCluster")
Automatic detection of KafkaClient client in registry
The component is capable of detecting the presence of an KafkaClient bean into the registry. If it’s the only instance of that type it will be used as client and you won’t have to define it as uri parameter. This may be really useful for smarter configuration of the endpoint.
Using a POJO as body
Sometimes build an AWS Request can be complex, because of multiple options. We introduce the possibility to use a POJO as body. In AWS MSK there are multiple operations you can submit, as an example for List clusters request, you can do something like:
from("direct:aws2-msk") .setBody(ListClustersRequest.builder().maxResults(10).build()) .to("aws2-msk://test?mskClient=#amazonMskClient&operation=listClusters&pojoRequest=true")
In this way you’ll pass the request directly without the need of passing headers and options specifically related to this operation.
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-msk</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-msk 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-msk-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
The component supports 14 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
camel.component.aws2-msk.access-key |
Amazon AWS Access Key |
String |
|
camel.component.aws2-msk.autowired-enabled |
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 |
camel.component.aws2-msk.configuration |
Component configuration. The option is a org.apache.camel.component.aws2.msk.MSK2Configuration type. |
MSK2Configuration |
|
camel.component.aws2-msk.enabled |
Whether to enable auto configuration of the aws2-msk component. This is enabled by default. |
Boolean |
|
camel.component.aws2-msk.lazy-start-producer |
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 |
camel.component.aws2-msk.msk-client |
To use a existing configured AWS MSK as client. The option is a software.amazon.awssdk.services.kafka.KafkaClient type. |
KafkaClient |
|
camel.component.aws2-msk.operation |
The operation to perform |
MSK2Operations |
|
camel.component.aws2-msk.pojo-request |
If we want to use a POJO request as body or not |
false |
Boolean |
camel.component.aws2-msk.proxy-host |
To define a proxy host when instantiating the MSK client |
String |
|
camel.component.aws2-msk.proxy-port |
To define a proxy port when instantiating the MSK client |
Integer |
|
camel.component.aws2-msk.proxy-protocol |
To define a proxy protocol when instantiating the MSK client |
Protocol |
|
camel.component.aws2-msk.region |
The region in which MSK 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 |
|
camel.component.aws2-msk.secret-key |
Amazon AWS Secret Key |
String |
|
camel.component.aws2-msk.trust-all-certificates |
If we want to trust all certificates in case of overriding the endpoint |
false |
Boolean |