AWS Simple Queue Service (SQS)
Since Camel 3.1
Both producer and consumer are supported
The AWS2 SQS component supports sending and receiving messages to Amazon’s SQS service.
Prerequisites
You must have a valid Amazon Web Services developer account, and be signed up to use Amazon SQS. More information is available at Amazon SQS.
URI Format
aws2-sqs://queueNameOrArn[?options]
The queue will be created if they don’t already exists.
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 Simple Queue Service (SQS) component supports 44 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
The hostname of the Amazon AWS cloud. |
amazonaws.com |
String |
|
Autowired To use the AmazonSQS as client. |
SqsClient |
||
Setting the autocreation of the queue. |
false |
boolean |
|
The AWS SQS default configuration. |
Sqs2Configuration |
||
Set the need for overriding the endpoint. This option needs to be used in combination with uriEndpointOverride option. |
false |
boolean |
|
The underlying protocol used to communicate with SQS. |
https |
String |
|
To define a proxy protocol when instantiating the SQS client. Enum values:
|
HTTPS |
Protocol |
|
Specify the queue owner aws account id when you need to connect the queue with different account owner. |
String |
||
The region in which SQS 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 |
||
If we want to trust all certificates in case of overriding the endpoint. |
false |
boolean |
|
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. |
String |
||
Set whether the SQS client should expect to load credentials on an AWS infra instance or to expect static credentials to be passed in. |
false |
boolean |
|
A list of attribute names to receive when consuming. Multiple names can be separated by comma. |
String |
||
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
boolean |
|
Allows you to use multiple threads to poll the sqs queue to increase throughput. |
1 |
int |
|
The default visibility timeout (in seconds). |
Integer |
||
Delete message from SQS after it has been read. |
true |
boolean |
|
Whether or not to send the DeleteMessage to the SQS queue if the exchange has property with key Sqs2Constants#SQS_DELETE_FILTERED (CamelAwsSqsDeleteFiltered) set to true. |
true |
boolean |
|
If enabled then a scheduled background task will keep extending the message visibility on SQS. This is needed if it takes a long time to process the message. If set to true defaultVisibilityTimeout must be set. See details at Amazon docs. |
false |
boolean |
|
The length of time, in seconds, for which Amazon SQS can reuse a data key to encrypt or decrypt messages before calling AWS KMS again. An integer representing seconds, between 60 seconds (1 minute) and 86,400 seconds (24 hours). Default: 300 (5 minutes). |
Integer |
||
The ID of an AWS-managed customer master key (CMK) for Amazon SQS or a custom CMK. |
String |
||
A list of message attribute names to receive when consuming. Multiple names can be separated by comma. |
String |
||
Define if Server Side Encryption is enabled or not on the queue. |
false |
boolean |
|
The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest. This only make sense if its different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently. |
Integer |
||
Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response. |
Integer |
||
Set the separator when passing a String to send batch message operation. |
, |
String |
|
Delay sending messages for a number of seconds. |
Integer |
||
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 |
|
Only for FIFO queues. Strategy for setting the messageDeduplicationId on the message. Can be one of the following options: useExchangeId, useContentBasedDeduplication. For the useContentBasedDeduplication option, no messageDeduplicationId will be set on the message. Enum values:
|
useExchangeId |
String |
|
Only for FIFO queues. Strategy for setting the messageGroupId on the message. Can be one of the following options: useConstant, useExchangeId, usePropertyValue. For the usePropertyValue option, the value of property CamelAwsMessageGroupId will be used. Enum values:
|
String |
||
What to do if sending to AWS SQS has more messages than AWS allows (currently only maximum 10 message headers is allowed). WARN will log a WARN about the limit is for each additional header, so the message can be sent to AWS. WARN_ONCE will only log one time a WARN about the limit is hit, and drop additional headers, so the message can be sent to AWS. IGNORE will ignore (no logging) and drop additional headers, so the message can be sent to AWS. FAIL will cause an exception to be thrown and the message is not sent to AWS. Enum values:
|
WARN |
String |
|
The operation to do in case the user don’t want to send only a message. Enum values:
|
Sqs2Operations |
||
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 |
|
Define if you want to apply delaySeconds option to the queue or on single messages. |
false |
boolean |
|
To define a proxy host when instantiating the SQS client. |
String |
||
To define a proxy port when instantiating the SQS client. |
Integer |
||
The maximumMessageSize (in bytes) an SQS message can contain for this queue. |
Integer |
||
The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. |
Integer |
||
The policy for this queue. It can be loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems. |
String |
||
To define the queueUrl explicitly. All other parameters, which would influence the queueUrl, are ignored. This parameter is intended to be used, to connect to a mock implementation of SQS, for testing purposes. |
String |
||
If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. |
Integer |
||
Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. |
String |
||
Amazon AWS Access Key. |
String |
||
Amazon AWS Secret Key. |
String |
Endpoint Options
The AWS Simple Queue Service (SQS) endpoint is configured using URI syntax:
aws2-sqs:queueNameOrArn
with the following path and query parameters:
Query Parameters (62 parameters)
Name | Description | Default | Type |
---|---|---|---|
The hostname of the Amazon AWS cloud. |
amazonaws.com |
String |
|
Autowired To use the AmazonSQS as client. |
SqsClient |
||
Setting the autocreation of the queue. |
false |
boolean |
|
To use a custom HeaderFilterStrategy to map headers to/from Camel. |
HeaderFilterStrategy |
||
Set the need for overriding the endpoint. This option needs to be used in combination with uriEndpointOverride option. |
false |
boolean |
|
The underlying protocol used to communicate with SQS. |
https |
String |
|
To define a proxy protocol when instantiating the SQS client. Enum values:
|
HTTPS |
Protocol |
|
Specify the queue owner aws account id when you need to connect the queue with different account owner. |
String |
||
The region in which SQS 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 |
||
If we want to trust all certificates in case of overriding the endpoint. |
false |
boolean |
|
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. |
String |
||
Set whether the SQS client should expect to load credentials on an AWS infra instance or to expect static credentials to be passed in. |
false |
boolean |
|
A list of attribute names to receive when consuming. Multiple names can be separated by comma. |
String |
||
Allows you to use multiple threads to poll the sqs queue to increase throughput. |
1 |
int |
|
The default visibility timeout (in seconds). |
Integer |
||
Delete message from SQS after it has been read. |
true |
boolean |
|
Whether or not to send the DeleteMessage to the SQS queue if the exchange has property with key Sqs2Constants#SQS_DELETE_FILTERED (CamelAwsSqsDeleteFiltered) set to true. |
true |
boolean |
|
If enabled then a scheduled background task will keep extending the message visibility on SQS. This is needed if it takes a long time to process the message. If set to true defaultVisibilityTimeout must be set. See details at Amazon docs. |
false |
boolean |
|
The length of time, in seconds, for which Amazon SQS can reuse a data key to encrypt or decrypt messages before calling AWS KMS again. An integer representing seconds, between 60 seconds (1 minute) and 86,400 seconds (24 hours). Default: 300 (5 minutes). |
Integer |
||
The ID of an AWS-managed customer master key (CMK) for Amazon SQS or a custom CMK. |
String |
||
Gets the maximum number of messages as a limit to poll at each polling. Is default unlimited, but use 0 or negative number to disable it as unlimited. |
int |
||
A list of message attribute names to receive when consuming. Multiple names can be separated by comma. |
String |
||
If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. |
false |
boolean |
|
Define if Server Side Encryption is enabled or not on the queue. |
false |
boolean |
|
The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest. This only make sense if its different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently. |
Integer |
||
Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response. |
Integer |
||
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
boolean |
|
To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
ExceptionHandler |
||
Sets the exchange pattern when the consumer creates an exchange. Enum values:
|
ExchangePattern |
||
A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. |
PollingConsumerPollStrategy |
||
Set the separator when passing a String to send batch message operation. |
, |
String |
|
Delay sending messages for a number of seconds. |
Integer |
||
Only for FIFO queues. Strategy for setting the messageDeduplicationId on the message. Can be one of the following options: useExchangeId, useContentBasedDeduplication. For the useContentBasedDeduplication option, no messageDeduplicationId will be set on the message. Enum values:
|
useExchangeId |
String |
|
Only for FIFO queues. Strategy for setting the messageGroupId on the message. Can be one of the following options: useConstant, useExchangeId, usePropertyValue. For the usePropertyValue option, the value of property CamelAwsMessageGroupId will be used. Enum values:
|
String |
||
What to do if sending to AWS SQS has more messages than AWS allows (currently only maximum 10 message headers is allowed). WARN will log a WARN about the limit is for each additional header, so the message can be sent to AWS. WARN_ONCE will only log one time a WARN about the limit is hit, and drop additional headers, so the message can be sent to AWS. IGNORE will ignore (no logging) and drop additional headers, so the message can be sent to AWS. FAIL will cause an exception to be thrown and the message is not sent to AWS. Enum values:
|
WARN |
String |
|
The operation to do in case the user don’t want to send only a message. Enum values:
|
Sqs2Operations |
||
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 |
|
Define if you want to apply delaySeconds option to the queue or on single messages. |
false |
boolean |
|
To define a proxy host when instantiating the SQS client. |
String |
||
To define a proxy port when instantiating the SQS client. |
Integer |
||
The maximumMessageSize (in bytes) an SQS message can contain for this queue. |
Integer |
||
The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. |
Integer |
||
The policy for this queue. It can be loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems. |
String |
||
To define the queueUrl explicitly. All other parameters, which would influence the queueUrl, are ignored. This parameter is intended to be used, to connect to a mock implementation of SQS, for testing purposes. |
String |
||
If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. |
Integer |
||
Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. |
String |
||
The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. |
int |
||
The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. |
int |
||
To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. |
int |
||
Milliseconds before the next poll. |
500 |
long |
|
If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. |
false |
boolean |
|
Milliseconds before the first poll starts. |
1000 |
long |
|
Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. |
0 |
long |
|
The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. Enum values:
|
TRACE |
LoggingLevel |
|
Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. |
ScheduledExecutorService |
||
To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler. |
none |
Object |
|
To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. |
Map |
||
Whether the scheduler should be auto started. |
true |
boolean |
|
Time unit for initialDelay and delay options. Enum values:
|
MILLISECONDS |
TimeUnit |
|
Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. |
true |
boolean |
|
Amazon AWS Access Key. |
String |
||
Amazon AWS Secret Key. |
String |
Required SQS component options
You have to provide the amazonSQSClient in the Registry or your accessKey and secretKey to access the Amazon’s SQS.
Batch Consumer
This component implements the Batch Consumer.
This allows you for instance to know how many messages exists in this batch and for instance let the Aggregator aggregate this number of messages.
Usage
Static credentials vs Default Credential Provider
You have the possibility of avoiding the usage of explicit static credentials, by specifying the useDefaultCredentialsProvider option and set it to true.
-
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.
For more information about this you can look at AWS credentials documentation
Message Headers
The AWS Simple Queue Service (SQS) component supports 8 message header(s), which is/are listed below:
Name | Description | Default | Type |
---|---|---|---|
CamelAwsSqsAttributes (consumer) Constant: |
A map of the attributes requested in ReceiveMessage to their respective values. |
Map |
|
CamelAwsSqsMessageAttributes (consumer) Constant: |
The Amazon SQS message attributes. |
Map |
|
Constant: |
The MD5 checksum of the Amazon SQS message. |
String |
|
Constant: |
The Amazon SQS message ID. |
String |
|
CamelAwsSqsReceiptHandle (common) Constant: |
The Amazon SQS message receipt handle. |
String |
|
CamelAwsSqsDelaySeconds (producer) Constant: |
The delay seconds that the Amazon SQS message can be see by others. |
Integer |
|
Constant: |
A string to use for filtering the list results. |
String |
|
Constant: |
The operation we want to perform. |
String |
Advanced AmazonSQS configuration
If your Camel Application is running behind a firewall or if you need to have more control over the SqsClient instance configuration, you can create your own instance, and configure Camel to use your instance by the bean id.
In the example below we use myClient as the bean id:
// crate my own instance of SqsClient
SqsClient sqs = ...
// register the client into Camel registry
camelContext.getRegistry().bind("myClient", sqs);
// refer to the custom client via myClient as the bean id
from("aws2-sqs://MyQueue?amazonSQSClient=#m4yClient&delay=5000&maxMessagesPerPoll=5")
.to("mock:result");
DelayQueue VS Delay for Single message
When the option delayQueue is set to true, the SQS Queue will be a DelayQueue with the DelaySeconds option as delay. For more information about DelayQueue you can read the AWS SQS documentation. One important information to take into account is the following:
-
For standard queues, the per-queue delay setting is not retroactive—changing the setting doesn’t affect the delay of messages already in the queue.
-
For FIFO queues, the per-queue delay setting is retroactive—changing the setting affects the delay of messages already in the queue.
as stated in the official documentation. If you want to specify a delay on single messages, you can ignore the delayQueue option, while you can set this option to true, if you need to add a fixed delay to all messages enqueued.
Server Side Encryption
There is a set of Server Side Encryption attributes for a queue. The related option are serverSideEncryptionEnabled, keyMasterKeyId and kmsDataKeyReusePeriod. The SSE is disabled by default. You need to explicitly set the option to true and set the related parameters as queue attributes.
JMS-style Selectors
SQS does not allow selectors, but you can effectively achieve this by
using the Camel Filter EIP and setting an
appropriate visibilityTimeout
. When SQS dispatches a message, it will
wait up to the visibility timeout before it will try to dispatch the
message to a different consumer unless a DeleteMessage is received. By
default, Camel will always send the DeleteMessage at the end of the
route, unless the route ended in failure. To achieve appropriate
filtering and not send the DeleteMessage even on successful completion
of the route, use a Filter:
from("aws2-sqs://MyQueue?amazonSQSClient=#client&defaultVisibilityTimeout=5000&deleteIfFiltered=false&deleteAfterRead=false")
.filter("${header.login} == true")
.setProperty(Sqs2Constants.SQS_DELETE_FILTERED, constant(true))
.to("mock:filter");
In the above code, if an exchange doesn’t have an appropriate header, it will not make it through the filter AND also not be deleted from the SQS queue. After 5000 milliseconds, the message will become visible to other consumers.
Note we must set the property Sqs2Constants.SQS_DELETE_FILTERED
to true
to
instruct Camel to send the DeleteMessage, if being filtered.
Send Message
from("direct:start")
.setBody(constant("Camel rocks!"))
.to("aws2-sqs://camel-1?accessKey=RAW(xxx)&secretKey=RAW(xxx)®ion=eu-west-1");
Send Batch Message
You can set a SendMessageBatchRequest
or an Iterable
from("direct:start")
.setHeader(SqsConstants.SQS_OPERATION, constant("sendBatchMessage"))
.process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
List c = new ArrayList();
c.add("team1");
c.add("team2");
c.add("team3");
c.add("team4");
exchange.getIn().setBody(c);
}
})
.to("aws2-sqs://camel-1?accessKey=RAW(xxx)&secretKey=RAW(xxx)®ion=eu-west-1");
As result you’ll get an exchange containing a SendMessageBatchResponse
instance, that you can examinate to check what messages were successfull and what not.
The id set on each message of the batch will be a Random UUID.
Delete single Message
Use deleteMessage operation to delete a single message. You’ll need to set a receipt handle header for the message you want to delete.
from("direct:start")
.setHeader(SqsConstants.SQS_OPERATION, constant("deleteMessage"))
.setHeader(SqsConstants.RECEIPT_HANDLE, constant("123456"))
.to("aws2-sqs://camel-1?accessKey=RAW(xxx)&secretKey=RAW(xxx)®ion=eu-west-1");
As result you’ll get an exchange containing a DeleteMessageResponse
instance, that you can use to check if the message was deleted or not.
List Queues
Use listQueues operation to list queues.
from("direct:start")
.setHeader(SqsConstants.SQS_OPERATION, constant("listQueues"))
.to("aws2-sqs://camel-1?accessKey=RAW(xxx)&secretKey=RAW(xxx)®ion=eu-west-1");
As result you’ll get an exchange containing a ListQueuesResponse
instance, that you can examinate to check the actual queues.
Purge Queue
Use purgeQueue operation to purge queue.
from("direct:start")
.setHeader(SqsConstants.SQS_OPERATION, constant("purgeQueue"))
.to("aws2-sqs://camel-1?accessKey=RAW(xxx)&secretKey=RAW(xxx)®ion=eu-west-1");
As result you’ll get an exchange containing a PurgeQueueResponse
instance.
Queue Autocreation
With the option autoCreateQueue
users are able to avoid the autocreation of an SQS Queue in case it doesn’t exist. The default for this option is false
.
If set to false any operation on a not-existent queue in AWS won’t be successful and an error will be returned.
Send Batch Message and Message Deduplication Strategy
In case you’re using a SendBatchMessage Operation, you can set two different kind of Message Deduplication Strategy: - useExchangeId - useContentBasedDeduplication
The first one will use a ExchangeIdMessageDeduplicationIdStrategy, that will use the Exchange ID as parameter The other one will use a NullMessageDeduplicationIdStrategy, that will use the body as deduplication element.
In case of send batch message operation, you’ll need to use the useContentBasedDeduplication
and on the Queue you’re pointing you’ll need to enable the content based deduplication
option.
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-sqs</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-sqs 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-sqs-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
The component supports 45 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
Amazon AWS Access Key. |
String |
||
The hostname of the Amazon AWS cloud. |
amazonaws.com |
String |
|
To use the AmazonSQS as client. The option is a software.amazon.awssdk.services.sqs.SqsClient type. |
SqsClient |
||
A list of attribute names to receive when consuming. Multiple names can be separated by comma. |
String |
||
Setting the autocreation of the queue. |
false |
Boolean |
|
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 |
|
Set the separator when passing a String to send batch message operation. |
, |
String |
|
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
Boolean |
|
Allows you to use multiple threads to poll the sqs queue to increase throughput. |
1 |
Integer |
|
The AWS SQS default configuration. The option is a org.apache.camel.component.aws2.sqs.Sqs2Configuration type. |
Sqs2Configuration |
||
The default visibility timeout (in seconds). |
Integer |
||
Define if you want to apply delaySeconds option to the queue or on single messages. |
false |
Boolean |
|
Delay sending messages for a number of seconds. |
Integer |
||
Delete message from SQS after it has been read. |
true |
Boolean |
|
Whether or not to send the DeleteMessage to the SQS queue if the exchange has property with key Sqs2Constants#SQS_DELETE_FILTERED (CamelAwsSqsDeleteFiltered) set to true. |
true |
Boolean |
|
Whether to enable auto configuration of the aws2-sqs component. This is enabled by default. |
Boolean |
||
If enabled then a scheduled background task will keep extending the message visibility on SQS. This is needed if it takes a long time to process the message. If set to true defaultVisibilityTimeout must be set. See details at Amazon docs. |
false |
Boolean |
|
The length of time, in seconds, for which Amazon SQS can reuse a data key to encrypt or decrypt messages before calling AWS KMS again. An integer representing seconds, between 60 seconds (1 minute) and 86,400 seconds (24 hours). Default: 300 (5 minutes). |
Integer |
||
The ID of an AWS-managed customer master key (CMK) for Amazon SQS or a custom CMK. |
String |
||
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 maximumMessageSize (in bytes) an SQS message can contain for this queue. |
Integer |
||
A list of message attribute names to receive when consuming. Multiple names can be separated by comma. |
String |
||
Only for FIFO queues. Strategy for setting the messageDeduplicationId on the message. Can be one of the following options: useExchangeId, useContentBasedDeduplication. For the useContentBasedDeduplication option, no messageDeduplicationId will be set on the message. |
useExchangeId |
String |
|
Only for FIFO queues. Strategy for setting the messageGroupId on the message. Can be one of the following options: useConstant, useExchangeId, usePropertyValue. For the usePropertyValue option, the value of property CamelAwsMessageGroupId will be used. |
String |
||
What to do if sending to AWS SQS has more messages than AWS allows (currently only maximum 10 message headers is allowed). WARN will log a WARN about the limit is for each additional header, so the message can be sent to AWS. WARN_ONCE will only log one time a WARN about the limit is hit, and drop additional headers, so the message can be sent to AWS. IGNORE will ignore (no logging) and drop additional headers, so the message can be sent to AWS. FAIL will cause an exception to be thrown and the message is not sent to AWS. |
WARN |
String |
|
The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. |
Integer |
||
The operation to do in case the user don’t want to send only a message. |
Sqs2Operations |
||
Set the need for overriding the endpoint. This option needs to be used in combination with uriEndpointOverride option. |
false |
Boolean |
|
The policy for this queue. It can be loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems. |
String |
||
The underlying protocol used to communicate with SQS. |
https |
String |
|
To define a proxy host when instantiating the SQS client. |
String |
||
To define a proxy port when instantiating the SQS client. |
Integer |
||
To define a proxy protocol when instantiating the SQS client. |
Protocol |
||
Specify the queue owner aws account id when you need to connect the queue with different account owner. |
String |
||
To define the queueUrl explicitly. All other parameters, which would influence the queueUrl, are ignored. This parameter is intended to be used, to connect to a mock implementation of SQS, for testing purposes. |
String |
||
If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. |
Integer |
||
Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. |
String |
||
The region in which SQS 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 |
||
Amazon AWS Secret Key. |
String |
||
Define if Server Side Encryption is enabled or not on the queue. |
false |
Boolean |
|
If we want to trust all certificates in case of overriding the endpoint. |
false |
Boolean |
|
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. |
String |
||
Set whether the SQS client should expect to load credentials on an AWS infra instance or to expect static credentials to be passed in. |
false |
Boolean |
|
The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest. This only make sense if its different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently. |
Integer |
||
Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response. |
Integer |