AWS 2 Elastic Container Service (ECS)
Since Camel 3.1
Only producer is supported
The AWS2 ECS component supports create, delete, describe and list clusters AWS ECS clusters instances.
Prerequisites
You must have a valid Amazon Web Services developer account, and be signed up to use Amazon ECS. More information is available at Amazon ECS.
The AWS2 ECS component is not supported in OSGI |
URI Format
aws2-ecs://label[?options]
You can append query options to the URI in the following format, ?options=value&option2=value&…
URI Options
The AWS 2 Elastic Container Service (ECS) component supports 14 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
autoDiscoverClient (common) |
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 |
boolean |
configuration (producer) |
Component configuration |
ECS2Configuration |
|
ecsClient (producer) |
To use a existing configured AWS ECS as client |
EcsClient |
|
lazyStartProducer (producer) |
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 |
operation (producer) |
Required The operation to perform. There are 4 enums and the value can be one of: listClusters, describeCluster, createCluster, deleteCluster |
ECS2Operations |
|
pojoRequest (producer) |
If we want to use a POJO request as body or not |
false |
boolean |
proxyHost (producer) |
To define a proxy host when instantiating the ECS client |
String |
|
proxyPort (producer) |
To define a proxy port when instantiating the ECS client |
Integer |
|
proxyProtocol (producer) |
To define a proxy protocol when instantiating the ECS client. There are 2 enums and the value can be one of: HTTP, HTTPS |
HTTPS |
Protocol |
region (producer) |
The region in which ECS 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 |
|
trustAllCertificates (producer) |
If we want to trust all certificates in case of overriding the endpoint |
false |
boolean |
basicPropertyBinding (advanced) |
Deprecated Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
boolean |
accessKey (security) |
Amazon AWS Access Key |
String |
|
secretKey (security) |
Amazon AWS Secret Key |
String |
The AWS 2 Elastic Container Service (ECS) endpoint is configured using URI syntax:
aws2-ecs:label
with the following path and query parameters:
Query Parameters (14 parameters):
Name | Description | Default | Type |
---|---|---|---|
autoDiscoverClient (common) |
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 |
boolean |
ecsClient (producer) |
To use a existing configured AWS ECS as client |
EcsClient |
|
lazyStartProducer (producer) |
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 |
operation (producer) |
Required The operation to perform. There are 4 enums and the value can be one of: listClusters, describeCluster, createCluster, deleteCluster |
ECS2Operations |
|
pojoRequest (producer) |
If we want to use a POJO request as body or not |
false |
boolean |
proxyHost (producer) |
To define a proxy host when instantiating the ECS client |
String |
|
proxyPort (producer) |
To define a proxy port when instantiating the ECS client |
Integer |
|
proxyProtocol (producer) |
To define a proxy protocol when instantiating the ECS client. There are 2 enums and the value can be one of: HTTP, HTTPS |
HTTPS |
Protocol |
region (producer) |
The region in which ECS 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 |
|
trustAllCertificates (producer) |
If we want to trust all certificates in case of overriding the endpoint |
false |
boolean |
basicPropertyBinding (advanced) |
Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
boolean |
synchronous (advanced) |
Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). |
false |
boolean |
accessKey (security) |
Amazon AWS Access Key |
String |
|
secretKey (security) |
Amazon AWS Secret Key |
String |
Required ECS component options
You have to provide the amazonECSClient in the Registry or your accessKey and secretKey to access the Amazon ECS service.
Usage
Producer Examples
-
listClusters: this operation will list the available clusters in ECS
from("direct:listClusters")
.to("aws2-ecs://test?ecsClient=#amazonEcsClient&operation=listClusters")
Automatic detection of EcsClient client in registry
The component is capable of detecting the presence of an EcsClient bean into the registry. If it’s the only instance of that type it will be used as client and you won’t have to define it as uri parameter. This may be really useful for smarter configuration of the endpoint.
Using a POJO as body
Sometimes build an AWS Request can be complex, because of multiple options. We introduce the possibility to use a POJO as body. In AWS ECS there are multiple operations you can submit, as an example for List cluster request, you can do something like:
from("direct:start") .setBody(ListClustersRequest.builder().maxResults(10).build()) .to("aws2-ecs://test?ecsClient=#amazonEcsClient&operation=listClusters&pojoRequest=true")
In this way you’ll pass the request directly without the need of passing headers and options specifically related to this operation.
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-ecs</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-ecs 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-ecs-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
The component supports 14 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
camel.component.aws2-ecs.access-key |
Amazon AWS Access Key |
String |
|
camel.component.aws2-ecs.autowired-enabled |
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 |
camel.component.aws2-ecs.configuration |
Component configuration. The option is a org.apache.camel.component.aws2.ecs.ECS2Configuration type. |
ECS2Configuration |
|
camel.component.aws2-ecs.ecs-client |
To use a existing configured AWS ECS as client. The option is a software.amazon.awssdk.services.ecs.EcsClient type. |
EcsClient |
|
camel.component.aws2-ecs.enabled |
Whether to enable auto configuration of the aws2-ecs component. This is enabled by default. |
Boolean |
|
camel.component.aws2-ecs.lazy-start-producer |
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 |
camel.component.aws2-ecs.operation |
The operation to perform |
ECS2Operations |
|
camel.component.aws2-ecs.pojo-request |
If we want to use a POJO request as body or not |
false |
Boolean |
camel.component.aws2-ecs.proxy-host |
To define a proxy host when instantiating the ECS client |
String |
|
camel.component.aws2-ecs.proxy-port |
To define a proxy port when instantiating the ECS client |
Integer |
|
camel.component.aws2-ecs.proxy-protocol |
To define a proxy protocol when instantiating the ECS client |
Protocol |
|
camel.component.aws2-ecs.region |
The region in which ECS 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 |
|
camel.component.aws2-ecs.secret-key |
Amazon AWS Secret Key |
String |
|
camel.component.aws2-ecs.trust-all-certificates |
If we want to trust all certificates in case of overriding the endpoint |
false |
Boolean |