camel-aws-lambda-kafka-connector sink configuration
When using camel-aws-lambda-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
<dependency>
<groupId>org.apache.camel.kafkaconnector</groupId>
<artifactId>camel-aws-lambda-kafka-connector</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel Kafka connector version -->
</dependency>
To use this Sink connector in Kafka connect you’ll need to set the following connector.class
connector.class=org.apache.camel.kafkaconnector.awslambda.CamelAwslambdaSinkConnector
The camel-aws-lambda sink connector supports 25 options, which are listed below.
Name | Description | Default | Required | Priority |
---|---|---|---|---|
camel.sink.path.function |
Name of the Lambda function. |
null |
true |
HIGH |
camel.sink.endpoint.autoDiscoverClient |
Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. |
true |
false |
MEDIUM |
camel.sink.endpoint.lazyStartProducer |
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 |
false |
MEDIUM |
camel.sink.endpoint.operation |
The operation to perform. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction One of: [listFunctions] [getFunction] [createAlias] [deleteAlias] [getAlias] [listAliases] [createFunction] [deleteFunction] [invokeFunction] [updateFunction] [createEventSourceMapping] [deleteEventSourceMapping] [listEventSourceMapping] [listTags] [tagResource] [untagResource] [publishVersion] [listVersions] |
"invokeFunction" |
false |
MEDIUM |
camel.sink.endpoint.region |
Amazon AWS Region. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You’ll need to use the name Regions.EU_WEST_1.name() |
null |
false |
MEDIUM |
camel.sink.endpoint.awsLambdaClient |
To use a existing configured AwsLambdaClient as client |
null |
false |
MEDIUM |
camel.sink.endpoint.basicPropertyBinding |
Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
false |
MEDIUM |
camel.sink.endpoint.synchronous |
Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). |
false |
false |
MEDIUM |
camel.sink.endpoint.proxyHost |
To define a proxy host when instantiating the Lambda client |
null |
false |
MEDIUM |
camel.sink.endpoint.proxyPort |
To define a proxy port when instantiating the Lambda client |
null |
false |
MEDIUM |
camel.sink.endpoint.proxyProtocol |
To define a proxy protocol when instantiating the Lambda client One of: [HTTP] [HTTPS] |
"HTTPS" |
false |
MEDIUM |
camel.sink.endpoint.accessKey |
Amazon AWS Access Key |
null |
false |
MEDIUM |
camel.sink.endpoint.secretKey |
Amazon AWS Secret Key |
null |
false |
MEDIUM |
camel.component.aws-lambda.autoDiscoverClient |
Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. |
true |
false |
MEDIUM |
camel.component.aws-lambda.configuration |
The AWS Lambda default configuration |
null |
false |
MEDIUM |
camel.component.aws-lambda.lazyStartProducer |
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 |
false |
MEDIUM |
camel.component.aws-lambda.operation |
The operation to perform. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction One of: [listFunctions] [getFunction] [createAlias] [deleteAlias] [getAlias] [listAliases] [createFunction] [deleteFunction] [invokeFunction] [updateFunction] [createEventSourceMapping] [deleteEventSourceMapping] [listEventSourceMapping] [listTags] [tagResource] [untagResource] [publishVersion] [listVersions] |
"invokeFunction" |
false |
MEDIUM |
camel.component.aws-lambda.region |
Amazon AWS Region. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You’ll need to use the name Regions.EU_WEST_1.name() |
null |
false |
MEDIUM |
camel.component.aws-lambda.awsLambdaClient |
To use a existing configured AwsLambdaClient as client |
null |
false |
MEDIUM |
camel.component.aws-lambda.basicPropertyBinding |
Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
false |
LOW |
camel.component.aws-lambda.proxyHost |
To define a proxy host when instantiating the Lambda client |
null |
false |
MEDIUM |
camel.component.aws-lambda.proxyPort |
To define a proxy port when instantiating the Lambda client |
null |
false |
MEDIUM |
camel.component.aws-lambda.proxyProtocol |
To define a proxy protocol when instantiating the Lambda client One of: [HTTP] [HTTPS] |
"HTTPS" |
false |
MEDIUM |
camel.component.aws-lambda.accessKey |
Amazon AWS Access Key |
null |
false |
MEDIUM |
camel.component.aws-lambda.secretKey |
Amazon AWS Secret Key |
null |
false |
MEDIUM |
The camel-aws-lambda sink connector has no converters out of the box.
The camel-aws-lambda sink connector has no transforms out of the box.
The camel-aws-lambda sink connector has no aggregation strategies out of the box.