AWS Elastic Kubernetes Service (EKS)
Since Camel 3.1
Only producer is supported
The AWS2 EKS component supports create, delete, describe and list clusters AWS EKS clusters instances.
Prerequisites
You must have a valid Amazon Web Services developer account, and be signed up to use Amazon EKS. More information is available at Amazon EKS.
The AWS2 EKS component is not supported in OSGI |
URI Format
aws2-eks://label[?options]
You can append query options to the URI in the following format, ?options=value&option2=value&…
URI Options
The AWS Elastic Kubernetes Service (EKS) component supports 16 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
configuration (producer) |
Component configuration |
EKS2Configuration |
|
eksClient (producer) |
Autowired To use a existing configured AWS EKS as client |
EksClient |
|
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 |
EKS2Operations |
|
overrideEndpoint (producer) |
Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option |
false |
boolean |
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 EKS client |
String |
|
proxyPort (producer) |
To define a proxy port when instantiating the EKS client |
Integer |
|
proxyProtocol (producer) |
To define a proxy protocol when instantiating the EKS client. There are 2 enums and the value can be one of: HTTP, HTTPS |
HTTPS |
Protocol |
region (producer) |
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() |
String |
|
trustAllCertificates (producer) |
If we want to trust all certificates in case of overriding the endpoint |
false |
boolean |
uriEndpointOverride (producer) |
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option |
String |
|
useDefaultCredentialsProvider (producer) |
Set whether the EKS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. |
false |
boolean |
autowiredEnabled (advanced) |
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 |
accessKey (security) |
Amazon AWS Access Key |
String |
|
secretKey (security) |
Amazon AWS Secret Key |
String |
The AWS Elastic Kubernetes Service (EKS) endpoint is configured using URI syntax:
aws2-eks:label
with the following path and query parameters:
Query Parameters (14 parameters):
Name | Description | Default | Type |
---|---|---|---|
eksClient (producer) |
Autowired To use a existing configured AWS EKS as client |
EksClient |
|
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 |
EKS2Operations |
|
overrideEndpoint (producer) |
Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option |
false |
boolean |
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 EKS client |
String |
|
proxyPort (producer) |
To define a proxy port when instantiating the EKS client |
Integer |
|
proxyProtocol (producer) |
To define a proxy protocol when instantiating the EKS client. There are 2 enums and the value can be one of: HTTP, HTTPS |
HTTPS |
Protocol |
region (producer) |
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() |
String |
|
trustAllCertificates (producer) |
If we want to trust all certificates in case of overriding the endpoint |
false |
boolean |
uriEndpointOverride (producer) |
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option |
String |
|
useDefaultCredentialsProvider (producer) |
Set whether the EKS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. |
false |
boolean |
accessKey (security) |
Amazon AWS Access Key |
String |
|
secretKey (security) |
Amazon AWS Secret Key |
String |
Required EKS component options
You have to provide the amazonEKSClient in the Registry or your accessKey and secretKey to access the Amazon EKS service.
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 evaluated by the EKS producer
Header | Type | Description |
---|---|---|
|
|
The limit number of results while listing clusters |
|
|
The operation we want to perform |
|
|
A key description to use while performing a createKey operation |
|
|
The cluster name |
|
|
The role ARN to use while creating the cluster |
|
|
The VPC config for the creations of an EKS cluster |
Producer Examples
-
listClusters: this operation will list the available clusters in EKS
from("direct:listClusters")
.to("aws2-eks://test?eksClient=#amazonEksClient&operation=listClusters")
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 EKS 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(12).build()) .to("aws2-eks://test?eksClient=#amazonEksClient&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-eks</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-eks 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-eks-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
The component supports 17 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
Amazon AWS Access Key. |
String |
||
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 |
|
Component configuration. The option is a org.apache.camel.component.aws2.eks.EKS2Configuration type. |
EKS2Configuration |
||
To use a existing configured AWS EKS as client. The option is a software.amazon.awssdk.services.eks.EksClient type. |
EksClient |
||
Whether to enable auto configuration of the aws2-eks component. This is enabled by default. |
Boolean |
||
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 operation to perform. |
EKS2Operations |
||
Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option. |
false |
Boolean |
|
If we want to use a POJO request as body or not. |
false |
Boolean |
|
To define a proxy host when instantiating the EKS client. |
String |
||
To define a proxy port when instantiating the EKS client. |
Integer |
||
To define a proxy protocol when instantiating the EKS client. |
Protocol |
||
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(). |
String |
||
Amazon AWS Secret Key. |
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 EKS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. |
false |
Boolean |