camel-aws-ecs-kafka-connector sink configuration

When using camel-aws-ecs-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-ecs-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.awsecs.CamelAwsecsSinkConnector

The camel-aws-ecs sink connector supports 24 options, which are listed below.

Name	Description	Default	Required	Priority
camel.sink.path.label	Logical name	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.accessKey	Amazon AWS Access Key	null	false	MEDIUM
camel.sink.endpoint.ecsClient	To use a existing configured AWS ECS as client	null	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 One of: [listClusters] [describeCluster] [createCluster] [deleteCluster]	null	true	HIGH
camel.sink.endpoint.proxyHost	To define a proxy host when instantiating the ECS client	null	false	MEDIUM
camel.sink.endpoint.proxyPort	To define a proxy port when instantiating the ECS client	null	false	MEDIUM
camel.sink.endpoint.proxyProtocol	To define a proxy protocol when instantiating the ECS client One of: [HTTP] [HTTPS]	"HTTPS"	false	MEDIUM
camel.sink.endpoint.region	The region in which ECS client needs to work. 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.secretKey	Amazon AWS Secret Key	null	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.component.aws-ecs.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-ecs.accessKey	Amazon AWS Access Key	null	false	MEDIUM
camel.component.aws-ecs.configuration	The component configuration	null	false	MEDIUM
camel.component.aws-ecs.ecsClient	To use a existing configured AWS ECS as client	null	false	MEDIUM
camel.component.aws-ecs.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-ecs.operation	The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster]	null	true	HIGH
camel.component.aws-ecs.proxyHost	To define a proxy host when instantiating the ECS client	null	false	MEDIUM
camel.component.aws-ecs.proxyPort	To define a proxy port when instantiating the ECS client	null	false	MEDIUM
camel.component.aws-ecs.proxyProtocol	To define a proxy protocol when instantiating the ECS client One of: [HTTP] [HTTPS]	"HTTPS"	false	MEDIUM
camel.component.aws-ecs.region	The region in which ECS client needs to work. 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-ecs.secretKey	Amazon AWS Secret Key	null	false	MEDIUM
camel.component.aws-ecs.autowiredEnabled	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	false	MEDIUM

Name

Description

Default

Required

Priority

camel.sink.path.label

Logical name

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.accessKey

Amazon AWS Access Key

null

false

MEDIUM

camel.sink.endpoint.ecsClient

To use a existing configured AWS ECS as client

null

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

MEDIUM

camel.sink.endpoint.operation

The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster]

null

true

HIGH

camel.sink.endpoint.proxyHost

To define a proxy host when instantiating the ECS client

null

false

MEDIUM

camel.sink.endpoint.proxyPort

To define a proxy port when instantiating the ECS client

null

false

MEDIUM

camel.sink.endpoint.proxyProtocol

To define a proxy protocol when instantiating the ECS client One of: [HTTP] [HTTPS]

"HTTPS"

false

MEDIUM

camel.sink.endpoint.region

The region in which ECS client needs to work. 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.secretKey

Amazon AWS Secret Key

null

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

MEDIUM

camel.component.aws-ecs.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-ecs.accessKey

Amazon AWS Access Key

null

false

MEDIUM

camel.component.aws-ecs.configuration

The component configuration

null

false

MEDIUM

camel.component.aws-ecs.ecsClient

To use a existing configured AWS ECS as client

null

false

MEDIUM

camel.component.aws-ecs.lazyStartProducer

false

MEDIUM

camel.component.aws-ecs.operation

The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster]

null

true

HIGH

camel.component.aws-ecs.proxyHost

To define a proxy host when instantiating the ECS client

null

false

MEDIUM

camel.component.aws-ecs.proxyPort

To define a proxy port when instantiating the ECS client

null

false

MEDIUM

camel.component.aws-ecs.proxyProtocol

To define a proxy protocol when instantiating the ECS client One of: [HTTP] [HTTPS]

"HTTPS"

false

MEDIUM

camel.component.aws-ecs.region

null

false

MEDIUM

camel.component.aws-ecs.secretKey

Amazon AWS Secret Key

null

false

MEDIUM

camel.component.aws-ecs.autowiredEnabled

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

false

MEDIUM

The camel-aws-ecs sink connector has no converters out of the box.

The camel-aws-ecs sink connector has no transforms out of the box.

The camel-aws-ecs sink connector has no aggregation strategies out of the box.