AWS Eventbridge
Since Camel 3.6
Both producer and consumer are supported
The AWS2 Eventbridge component supports assumeRole operation. AWS Eventbridge.
Prerequisites
You must have a valid Amazon Web Services developer account, and be signed up to use Amazon Eventbridge. More information is available at Amazon Eventbridge.
| To create a rule that triggers on an action by an AWS service that does not emit events, you can base the rule on API calls made by that service. The API calls are recorded by AWS CloudTrail, so you’ll need to have CloudTrail enabled. For more information, check Services Supported by CloudTrail Event History. |
URI Format
aws2-eventbridge://label[?options]
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
At the component level, you set general and shared configurations that are, then, inherited by the endpoints. It is the highest configuration level.
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.
You can configure components using:
-
the Component DSL.
-
in a configuration file (
application.properties,*.yamlfiles, etc). -
directly in the Java code.
Configuring Endpoint Options
You usually spend more time setting up endpoints because they have many options. These options help you customize what you want the endpoint to do. The options are also categorized into whether the endpoint is used as a consumer (from), as a producer (to), or 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.
Property placeholders provide a few benefits:
-
They help prevent using hardcoded urls, port numbers, sensitive information, and other settings.
-
They allow externalizing the configuration from the code.
-
They help the code to become more flexible and reusable.
The following two sections list all the options, firstly for the component followed by the endpoint.
Component Options
The AWS Eventbridge component supports 31 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
Component configuration. | EventbridgeConfiguration | ||
EventPattern File. | String | ||
Required The operation to perform. Enum values:
| putRule | EventbridgeOperations | |
Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option. | false | boolean | |
If we want to use a POJO request as body or not. | false | boolean | |
The region in which the Eventbridge 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(). Enum values:
| String | ||
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. | String | ||
Whether to auto-create an SQS queue and wire it as an EventBridge rule target. | true | boolean | |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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 | |
Whether to delete the auto-created SQS queue and remove the EventBridge target on shutdown. | true | boolean | |
The maximum number of messages to receive per poll from SQS. | 10 | int | |
The URL of an existing SQS queue to use as EventBridge target. If not specified, a queue is auto-created when autoCreateQueue is true. | String | ||
The EventBridge rule name to consume events from. Required for consumer. | String | ||
The duration (in seconds) that received SQS messages are hidden from subsequent receive requests. | 30 | int | |
The duration (in seconds) for which the SQS receive call waits for messages (long polling). | 20 | int | |
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 | |
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 | |
Autowired To use an existing configured AWS Eventbridge client. | EventBridgeClient | ||
Used for enabling or disabling all consumer based health checks from this component. | true | boolean | |
Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true. | true | boolean | |
To define a proxy host when instantiating the Eventbridge client. | String | ||
To define a proxy port when instantiating the Eventbridge client. | Integer | ||
To define a proxy protocol when instantiating the Eventbridge client. Enum values:
| HTTPS | Protocol | |
Amazon AWS Access Key. | String | ||
If using a profile credentials provider this parameter will set the profile name. | String | ||
Amazon AWS Secret Key. | String | ||
Amazon AWS Session Token used when the user needs to assume an IAM role. | String | ||
If we want to trust all certificates in case of overriding the endpoint. | false | boolean | |
Set whether the Eventbridge client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | boolean | |
Set whether the Eventbridge client should expect to load credentials through a profile credentials provider. | false | boolean | |
Set whether the Eventbridge client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Eventbridge. | false | boolean |
Endpoint Options
The AWS Eventbridge endpoint is configured using URI syntax:
aws2-eventbridge://eventbusNameOrArn
With the following path and query parameters:
Query Parameters (45 parameters)
| Name | Description | Default | Type |
|---|---|---|---|
EventPattern File. | String | ||
Required The operation to perform. Enum values:
| putRule | EventbridgeOperations | |
Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option. | false | boolean | |
If we want to use a POJO request as body or not. | false | boolean | |
The region in which the Eventbridge 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(). Enum values:
| String | ||
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. | String | ||
Whether to auto-create an SQS queue and wire it as an EventBridge rule target. | true | boolean | |
Whether to delete the auto-created SQS queue and remove the EventBridge target on shutdown. | true | boolean | |
The maximum number of messages to receive per poll from SQS. | 10 | int | |
The URL of an existing SQS queue to use as EventBridge target. If not specified, a queue is auto-created when autoCreateQueue is true. | String | ||
The EventBridge rule name to consume events from. Required for consumer. | 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 | |
The duration (in seconds) that received SQS messages are hidden from subsequent receive requests. | 30 | int | |
The duration (in seconds) for which the SQS receive call waits for messages (long polling). | 20 | int | |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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 | ||
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 | |
Autowired To use an existing configured AWS Eventbridge client. | EventBridgeClient | ||
To define a proxy host when instantiating the Eventbridge client. | String | ||
To define a proxy port when instantiating the Eventbridge client. | Integer | ||
To define a proxy protocol when instantiating the Eventbridge client. Enum values:
| HTTPS | Protocol | |
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. This is a multi-value option with prefix: 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 | ||
If using a profile credentials provider this parameter will set the profile name. | String | ||
Amazon AWS Secret Key. | String | ||
Amazon AWS Session Token used when the user needs to assume an IAM role. | String | ||
If we want to trust all certificates in case of overriding the endpoint. | false | boolean | |
Set whether the Eventbridge client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | boolean | |
Set whether the Eventbridge client should expect to load credentials through a profile credentials provider. | false | boolean | |
Set whether the Eventbridge client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Eventbridge. | false | boolean |
Message Headers
The AWS Eventbridge component supports 17 message header(s), which is/are listed below:
| Name | Description | Default | Type |
|---|---|---|---|
CamelAwsEventbridgeOperation (common) Constant: | The operation we want to perform. | String | |
CamelAwsEventbridgeRuleName (common) Constant: | The name of the rule. | String | |
CamelAwsEventbridgeRuleNamePrefix (common) Constant: | The prefix matching the rule name. | String | |
CamelAwsEventbridgeEventPattern (common) Constant: | The event pattern. | String | |
CamelAwsEventbridgeTargets (common) Constant: | The targets to update or add to the rule. | Collection | |
CamelAwsEventbridgeTargetsIds (common) Constant: | The IDs of the targets to remove from the rule. | Collection | |
CamelAwsEventbridgeTargetArn (common) Constant: | The Amazon Resource Name (ARN) of the target resource. | String | |
CamelAwsEventbridgeResourcesArn (common) Constant: | Comma separated list of Amazon Resource Names (ARN) of the resources related to Event. | String | |
CamelAwsEventbridgeSource (common) Constant: | The source related to Event. | String | |
CamelAwsEventbridgeDetailType (common) Constant: | The detail type related to Event. | String | |
CamelAwsEventbridgeNextToken (listRules listTargetsByRule listRuleNamesByTarget) Constant: | The token for the next set of results. | String | |
CamelAwsEventbridgeLimit (listRules listTargetsByRule listRuleNamesByTarget) Constant: | The maximum number of results to return. | Integer | |
CamelAwsEventbridgeIsTruncated (listRules listTargetsByRule listRuleNamesByTarget) Constant: | Whether the response has more results (is truncated). | Boolean | |
CamelAwsEventbridgeRuleArn (putRule describeRule) Constant: | The Amazon Resource Name (ARN) of the rule. | String | |
CamelAwsEventbridgeFailedEntryCount (putEvent putTargets removeTargets) Constant: | The number of failed entries in the response. | Integer | |
CamelAwsEventbridgeMessageId (consumer) Constant: | The SQS message ID. | String | |
CamelAwsEventbridgeReceiptHandle (consumer) Constant: | The SQS receipt handle for message deletion. | String |
Usage
Static credentials, Default Credential Provider and Profile Credentials Provider
You have the possibility of avoiding the usage of explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_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_URIis set. -
Amazon EC2 Instance profile credentials.
You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of static, default and profile credentials could be used at the same time.
For more information about this you can look at AWS credentials documentation
AWS2-Eventbridge Producer operations
Camel-AWS2-Eventbridge component provides the following operation on the producer side:
-
putRule
-
putTargets
-
removeTargets
-
deleteRule
-
enableRule
-
disableRule
-
listRules
-
describeRule
-
listTargetsByRule
-
listRuleNamesByTarget
-
putEvent
-
PutRule: this operation creates a rule related to an eventbus
from("direct:putRule").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
}
})
.to("aws2-eventbridge://test?operation=putRule&eventPatternFile=file:src/test/resources/eventpattern.json")
.to("mock:result"); This operation will create a rule named firstrule, and it will use a json file for defining the EventPattern.
-
PutTargets: this operation will add a target to the rule
from("direct:start").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
Target target = Target.builder().id("sqs-queue").arn("arn:aws:sqs:eu-west-1:780410022472:camel-connector-test")
.build();
List<Target> targets = new ArrayList<Target>();
targets.add(target);
exchange.getIn().setHeader(EventbridgeConstants.TARGETS, targets);
}
})
.to("aws2-eventbridge://test?operation=putTargets")
.to("mock:result"); This operation will add the target sqs-queue with the arn reported to the targets of the firstrule rule.
-
RemoveTargets: this operation will remove a collection of targets from the rule
from("direct:start").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
List<String> ids = new ArrayList<String>();
targets.add("sqs-queue");
exchange.getIn().setHeader(EventbridgeConstants.TARGETS_IDS, targets);
}
})
.to("aws2-eventbridge://test?operation=removeTargets")
.to("mock:result"); This operation will remove the target sqs-queue from the firstrule rule.
-
DeleteRule: this operation will delete a rule related to an eventbus
from("direct:start").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
}
})
.to("aws2-eventbridge://test?operation=deleteRule")
.to("mock:result"); This operation will remove the firstrule rule from the test eventbus.
-
EnableRule: this operation will enable a rule related to an eventbus
from("direct:start").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
}
})
.to("aws2-eventbridge://test?operation=enableRule")
.to("mock:result"); This operation will enable the firstrule rule from the test eventbus.
-
DisableRule: this operation will disable a rule related to an eventbus
from("direct:start").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
}
})
.to("aws2-eventbridge://test?operation=disableRule")
.to("mock:result"); This operation will disable the firstrule rule from the test eventbus.
-
ListRules: this operation will list all the rules related to an eventbus with prefix first
from("direct:start").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME_PREFIX, "first");
}
})
.to("aws2-eventbridge://test?operation=listRules")
.to("mock:result"); This operation will list all the rules with prefix first from the test eventbus.
-
DescribeRule: this operation will describe a specified rule related to an eventbus
from("direct:start").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
}
})
.to("aws2-eventbridge://test?operation=describeRule")
.to("mock:result"); This operation will describe the firstrule rule from the test eventbus.
-
ListTargetsByRule: this operation will return a list of targets associated with a rule
from("direct:start").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
}
})
.to("aws2-eventbridge://test?operation=listTargetsByRule")
.to("mock:result"); this operation will return a list of targets associated with the firstrule rule.
-
ListRuleNamesByTarget: this operation will return a list of rules associated with a target
from("direct:start").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(EventbridgeConstants.TARGET_ARN, "firstrule");
}
})
.to("aws2-eventbridge://test?operation=listRuleNamesByTarget")
.to("mock:result"); this operation will return a list of rules associated with a target.
-
PutEvent: this operation will send an event to the Servicebus
from("direct:start").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(EventbridgeConstants.EVENT_RESOURCES_ARN, "arn:aws:sqs:eu-west-1:780410022472:camel-connector-test");
exchange.getIn().setHeader(EventbridgeConstants.EVENT_SOURCE, "com.pippo");
exchange.getIn().setHeader(EventbridgeConstants.EVENT_DETAIL_TYPE, "peppe");
exchange.getIn().setBody("Test Event");
}
})
.to("aws2-eventbridge://test?operation=putEvent")
.to("mock:result"); this operation will return a list of entries with related ID sent to servicebus.
Consuming Events from EventBridge
Since Camel 4.19, the component supports consuming events from EventBridge rules using an SQS-backed polling pattern.
AWS EventBridge is an event router, not a message queue — it does not provide a pull-based API. The consumer works by wiring an SQS queue as a target of the specified EventBridge rule and then polling that queue for events. This is the standard AWS pattern for programmatically consuming EventBridge events.
How It Works
-
On startup the consumer creates an SQS queue (unless you provide one via
queueUrl). -
It sets an SQS queue policy that allows EventBridge to send messages.
-
It adds the queue as a target of the EventBridge rule specified by
ruleName. -
It polls the SQS queue on schedule, delivering each event into the Camel route.
-
Successfully processed messages are deleted from the queue; failed messages remain for retry.
-
On shutdown the target is removed and the auto-created queue is deleted (configurable).
Consumer Configuration Options
| Option | Default | Type | Description |
|---|---|---|---|
| String | Required. The EventBridge rule name to consume events from. | |
| String | URL of an existing SQS queue to use. If omitted, a queue is auto-created. | |
|
| boolean | Whether to auto-create an SQS queue and wire it as the rule target. |
|
| boolean | Whether to delete the auto-created queue and remove the EventBridge target on shutdown. |
|
| int | Maximum number of SQS messages to receive per poll cycle. |
|
| int | SQS long-polling wait time in seconds. |
|
| int | Seconds that received messages are hidden from subsequent polls. |
Standard ScheduledPollConsumer options (delay, initialDelay, greedy, etc.) are also available.
Consumer Example — Auto-Created Queue
from("aws2-eventbridge://default?ruleName=my-rule&delay=5000")
.log("Received EventBridge event: ${body}")
.to("direct:process"); The consumer auto-creates an SQS queue, wires it to the my-rule EventBridge rule, and polls every 5 seconds.
Consumer Example — User-Provided Queue
from("aws2-eventbridge://default?ruleName=my-rule"
+ "&autoCreateQueue=false"
+ "&queueUrl=https://sqs.us-east-1.amazonaws.com/123456789012/my-queue")
.log("Received: ${body}")
.to("direct:process"); Use this when you manage the SQS queue and its policy yourself.
Consumer Example — Combined Producer and Consumer
// First create the rule
from("direct:setup")
.to("aws2-eventbridge://default?operation=putRule"
+ "&eventPatternFile=file:eventpattern.json");
// Consume events matching the rule
from("aws2-eventbridge://default?ruleName=my-rule&delay=2000")
.log("Event: ${body}")
.to("mock:events"); 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-eventbridge</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-eventbridge 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-eventbridge-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency> The component supports 32 options, which are listed below.