AWS 2 Identity and Access Management (IAM)
Since Camel 3.1
Only producer is supported
The AWS2 IAM component supports create, run, start, stop and terminate AWS IAM instances.
Prerequisites
You must have a valid Amazon Web Services developer account, and be signed up to use Amazon IAM. More information is available at Amazon IAM.
The AWS2 IAM component is not supported in OSGI |
URI Format
aws2-iam://label[?options]
You can append query options to the URI in the following format, ?options=value&option2=value&…
URI Options
The AWS 2 Identity and Access Management (IAM) component supports 13 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
configuration (producer) |
Component configuration |
IAM2Configuration |
|
iamClient (producer) |
Autowired To use a existing configured AWS IAM as client |
IamClient |
|
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) |
The operation to perform. You can configure a default operation on the component level, or the operation as part of the endpoint, or via a message header with the key CamelAwsIAMOperation. There are 13 enums and the value can be one of: listAccessKeys, createUser, deleteUser, getUser, listUsers, createAccessKey, deleteAccessKey, updateAccessKey, createGroup, deleteGroup, listGroups, addUserToGroup, removeUserFromGroup |
IAM2Operations |
|
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 IAM client |
String |
|
proxyPort (producer) |
To define a proxy port when instantiating the IAM client |
Integer |
|
proxyProtocol (producer) |
To define a proxy protocol when instantiating the IAM client. There are 2 enums and the value can be one of: HTTP, HTTPS |
HTTPS |
Protocol |
region (producer) |
The region in which IAM 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() |
aws-global |
String |
trustAllCertificates (producer) |
If we want to trust all certificates in case of overriding the endpoint |
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 2 Identity and Access Management (IAM) endpoint is configured using URI syntax:
aws2-iam:label
with the following path and query parameters:
Query Parameters (12 parameters):
Name | Description | Default | Type |
---|---|---|---|
iamClient (producer) |
Autowired To use a existing configured AWS IAM as client |
IamClient |
|
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) |
The operation to perform. You can configure a default operation on the component level, or the operation as part of the endpoint, or via a message header with the key CamelAwsIAMOperation. There are 13 enums and the value can be one of: listAccessKeys, createUser, deleteUser, getUser, listUsers, createAccessKey, deleteAccessKey, updateAccessKey, createGroup, deleteGroup, listGroups, addUserToGroup, removeUserFromGroup |
IAM2Operations |
|
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 IAM client |
String |
|
proxyPort (producer) |
To define a proxy port when instantiating the IAM client |
Integer |
|
proxyProtocol (producer) |
To define a proxy protocol when instantiating the IAM client. There are 2 enums and the value can be one of: HTTP, HTTPS |
HTTPS |
Protocol |
region (producer) |
The region in which IAM 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() |
aws-global |
String |
trustAllCertificates (producer) |
If we want to trust all certificates in case of overriding the endpoint |
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 IAM component options
You have to provide the amazonKmsClient in the Registry or your accessKey and secretKey to access the Amazon IAM service.
Usage
Message headers evaluated by the IAM producer
Header | Type | Description |
---|---|---|
|
|
The operation we want to perform |
|
|
The username for the user you want to manage |
|
|
The accessKey you want to manage |
|
|
The Status of the AccessKey you want to set, possible value are active and inactive |
|
|
The name of an AWS IAM Group |
|
|
The path of an AWS IAM Group |
The AWS2 IAM component works on the aws-global region and it has aws-global as default region |
Producer Examples
-
createUser: this operation will create a user in IAM
from("direct:createUser")
.setHeader(IAM2Constants.USERNAME, constant("camel"))
.to("aws2-iam://test?iamClient=#amazonIAMClient&operation=createUser")
-
deleteUser: this operation will delete a user in IAM
from("direct:deleteUser")
.setHeader(IAM2Constants.USERNAME, constant("camel"))
.to("aws2-iam://test?iamClient=#amazonIAMClient&operation=deleteUser")
-
listUsers: this operation will list the users in IAM
from("direct:listUsers")
.to("aws2-iam://test?iamClient=#amazonIAMClient&operation=listUsers")
-
createGroup: this operation will add a group in IAM
from("direct:deleteUser")
.setHeader(IAM2Constants.GROUP_NAME, constant("camel"))
.to("aws2-iam://test?iamClient=#amazonIAMClient&operation=createGroup")
-
deleteGroup: this operation will delete a group in IAM
from("direct:deleteUser")
.setHeader(IAM2Constants.GROUP_NAME, constant("camel"))
.to("aws2-iam://test?iamClient=#amazonIAMClient&operation=deleteGroup")
-
listGroups: this operation will list the groups in IAM
from("direct:listUsers")
.to("aws2-iam://test?iamClient=#amazonIAMClient&operation=listGroups")
Automatic detection of IamClient client in registry
The component is capable of detecting the presence of an IamClient 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 IAM there are multiple operations you can submit, as an example for Create User request, you can do something like:
from("direct:createUser") .setBody(CreateUserRequest.builder().userName("camel").build()) .to("aws2-iam://test?iamClient=#amazonIAMClient&operation=createUser&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-iam</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-iam 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-iam-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-iam.access-key |
Amazon AWS Access Key |
String |
|
camel.component.aws2-iam.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-iam.configuration |
Component configuration. The option is a org.apache.camel.component.aws2.iam.IAM2Configuration type. |
IAM2Configuration |
|
camel.component.aws2-iam.enabled |
Whether to enable auto configuration of the aws2-iam component. This is enabled by default. |
Boolean |
|
camel.component.aws2-iam.iam-client |
To use a existing configured AWS IAM as client. The option is a software.amazon.awssdk.services.iam.IamClient type. |
IamClient |
|
camel.component.aws2-iam.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-iam.operation |
The operation to perform. You can configure a default operation on the component level, or the operation as part of the endpoint, or via a message header with the key CamelAwsIAMOperation. |
IAM2Operations |
|
camel.component.aws2-iam.pojo-request |
If we want to use a POJO request as body or not |
false |
Boolean |
camel.component.aws2-iam.proxy-host |
To define a proxy host when instantiating the IAM client |
String |
|
camel.component.aws2-iam.proxy-port |
To define a proxy port when instantiating the IAM client |
Integer |
|
camel.component.aws2-iam.proxy-protocol |
To define a proxy protocol when instantiating the IAM client |
Protocol |
|
camel.component.aws2-iam.region |
The region in which IAM 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() |
aws-global |
String |
camel.component.aws2-iam.secret-key |
Amazon AWS Secret Key |
String |
|
camel.component.aws2-iam.trust-all-certificates |
If we want to trust all certificates in case of overriding the endpoint |
false |
Boolean |