camel-aws2-kms-kafka-connector sink configuration
Connector Description: Manage keys stored in AWS KMS instances.
When using camel-aws2-kms-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-aws2-kms-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.aws2kms.CamelAws2kmsSinkConnector
The camel-aws2-kms sink connector supports 39 options, which are listed below.
Name | Description | Default | Priority |
---|---|---|---|
Required Logical name. | HIGH | ||
Required The operation to perform One of: [listKeys] [createKey] [disableKey] [scheduleKeyDeletion] [describeKey] [enableKey]. Enum values:
| HIGH | ||
Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option. | false | MEDIUM | |
If we want to use a POJO request as body or not. | false | MEDIUM | |
The region in which EKS 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() One of: [ap-south-2] [ap-south-1] [eu-south-1] [eu-south-2] [us-gov-east-1] [me-central-1] [il-central-1] [ca-central-1] [eu-central-1] [us-iso-west-1] [eu-central-2] [eu-isoe-west-1] [us-west-1] [us-west-2] [af-south-1] [eu-north-1] [eu-west-3] [eu-west-2] [eu-west-1] [ap-northeast-3] [ap-northeast-2] [ap-northeast-1] [me-south-1] [sa-east-1] [ap-east-1] [cn-north-1] [ca-west-1] [us-gov-west-1] [ap-southeast-1] [ap-southeast-2] [us-iso-east-1] [ap-southeast-3] [ap-southeast-4] [us-east-1] [us-east-2] [cn-northwest-1] [us-isob-east-1] [aws-global] [aws-cn-global] [aws-us-gov-global] [aws-iso-global] [aws-iso-b-global]. Enum values:
| MEDIUM | ||
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. | MEDIUM | ||
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 | |
To use an existing configured AWS KMS client. | MEDIUM | ||
To define a proxy host when instantiating the KMS client. | MEDIUM | ||
To define a proxy port when instantiating the KMS client. | MEDIUM | ||
To define a proxy protocol when instantiating the KMS client One of: [HTTP] [HTTPS]. Enum values:
| "HTTPS" | MEDIUM | |
Amazon AWS Access Key. | MEDIUM | ||
If using a profile credentials provider, this parameter will set the profile name. | MEDIUM | ||
Amazon AWS Secret Key. | MEDIUM | ||
Amazon AWS Session Token used when the user needs to assume an IAM role. | MEDIUM | ||
If we want to trust all certificates in case of overriding the endpoint. | false | MEDIUM | |
Set whether the KMS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | MEDIUM | |
Set whether the KMS client should expect to load credentials through a profile credentials provider. | false | MEDIUM | |
Set whether the KMS client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume a IAM role for doing operations in KMS. | false | MEDIUM | |
Component configuration. | MEDIUM | ||
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 | |
Required The operation to perform One of: [listKeys] [createKey] [disableKey] [scheduleKeyDeletion] [describeKey] [enableKey]. Enum values:
| HIGH | ||
Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option. | false | MEDIUM | |
If we want to use a POJO request as body or not. | false | MEDIUM | |
The region in which EKS 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() One of: [ap-south-2] [ap-south-1] [eu-south-1] [eu-south-2] [us-gov-east-1] [me-central-1] [il-central-1] [ca-central-1] [eu-central-1] [us-iso-west-1] [eu-central-2] [eu-isoe-west-1] [us-west-1] [us-west-2] [af-south-1] [eu-north-1] [eu-west-3] [eu-west-2] [eu-west-1] [ap-northeast-3] [ap-northeast-2] [ap-northeast-1] [me-south-1] [sa-east-1] [ap-east-1] [cn-north-1] [ca-west-1] [us-gov-west-1] [ap-southeast-1] [ap-southeast-2] [us-iso-east-1] [ap-southeast-3] [ap-southeast-4] [us-east-1] [us-east-2] [cn-northwest-1] [us-isob-east-1] [aws-global] [aws-cn-global] [aws-us-gov-global] [aws-iso-global] [aws-iso-b-global]. Enum values:
| MEDIUM | ||
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. | MEDIUM | ||
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 | MEDIUM | |
To use an existing configured AWS KMS client. | MEDIUM | ||
To define a proxy host when instantiating the KMS client. | MEDIUM | ||
To define a proxy port when instantiating the KMS client. | MEDIUM | ||
To define a proxy protocol when instantiating the KMS client One of: [HTTP] [HTTPS]. Enum values:
| "HTTPS" | MEDIUM | |
Amazon AWS Access Key. | MEDIUM | ||
If using a profile credentials provider, this parameter will set the profile name. | MEDIUM | ||
Amazon AWS Secret Key. | MEDIUM | ||
Amazon AWS Session Token used when the user needs to assume an IAM role. | MEDIUM | ||
If we want to trust all certificates in case of overriding the endpoint. | false | MEDIUM | |
Set whether the KMS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | MEDIUM | |
Set whether the KMS client should expect to load credentials through a profile credentials provider. | false | MEDIUM | |
Set whether the KMS client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume a IAM role for doing operations in KMS. | false | MEDIUM |
The camel-aws2-kms sink connector has no converters out of the box.
The camel-aws2-kms sink connector has no transforms out of the box.
The camel-aws2-kms sink connector has no aggregation strategies out of the box.