AWS 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.
URI Format
aws2-iam://label[?options]
You can append query options to the URI in the following format:
?options=value&option2=value&…
The AWS2 IAM component works on the aws-global region, and it has aws-global as the default region |
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
,*.yaml
files, 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 Identity and Access Management (IAM) component supports 22 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
Component configuration. | IAM2Configuration | ||
Autowired To use an existing configured AWS IAM client. | IamClient | ||
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. 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. Enum values:
| IAM2Operations | ||
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 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(). Enum values:
| aws-global | String | |
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. | 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 | |
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 IAM client. | String | ||
To define a proxy port when instantiating the IAM client. | Integer | ||
To define a proxy protocol when instantiating the IAM 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 IAM 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 IAM client should expect to load credentials through a profile credentials provider. | false | boolean | |
Set whether the IAM client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume a IAM role for doing operations in IAM. | false | boolean |
Endpoint Options
The AWS Identity and Access Management (IAM) endpoint is configured using URI syntax:
aws2-iam:label
With the following path and query parameters:
Query Parameters (18 parameters)
Name | Description | Default | Type |
---|---|---|---|
Autowired To use an existing configured AWS IAM client. | IamClient | ||
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. Enum values:
| IAM2Operations | ||
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 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(). Enum values:
| aws-global | String | |
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. | 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 | |
To define a proxy host when instantiating the IAM client. | String | ||
To define a proxy port when instantiating the IAM client. | Integer | ||
To define a proxy protocol when instantiating the IAM 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 IAM 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 IAM client should expect to load credentials through a profile credentials provider. | false | boolean | |
Set whether the IAM client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume a IAM role for doing operations in IAM. | false | boolean |
Required IAM component options
You have to provide the amazonKmsClient in the Registry or your accessKey and secretKey to access the Amazon IAM service.
Message Headers
The AWS Identity and Access Management (IAM) component supports 6 message header(s), which is/are listed below:
Name | Description | Default | Type |
---|---|---|---|
CamelAwsIAMOperation (producer) Constant: | The operation we want to perform. | String | |
CamelAwsIAMUsername (producer) Constant: | The username for the user you want to manage. | String | |
CamelAwsIAMAccessKeyID (producer) Constant: | The accessKey you want to manage. | String | |
CamelAwsIAMAccessKeyStatus (producer) Constant: | The Status of the AccessKey you want to set, possible value are active and inactive. | String | |
CamelAwsIAMGroupName (producer) Constant: | The name of an AWS IAM Group. | String | |
CamelAwsIAMGroupPath (producer) Constant: | The path of an AWS IAM Group. | 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.accessKeyId
andaws.secretKey
. -
Environment variables -
AWS_ACCESS_KEY_ID
andAWS_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.
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
Examples
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")
Using a POJO as body
Sometimes building an AWS Request can be complex because of multiple options. We introduce the possibility to use a POJO as a 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 23 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.iam.IAM2Configuration type. | IAM2Configuration | ||
Whether to enable auto configuration of the aws2-iam component. This is enabled by default. | Boolean | ||
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 use an existing configured AWS IAM client. The option is a software.amazon.awssdk.services.iam.IamClient type. | IamClient | ||
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. 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 | ||
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 | |
If using a profile credentials provider, this parameter will set the profile name. | String | ||
To define a proxy host when instantiating the IAM client. | String | ||
To define a proxy port when instantiating the IAM client. | Integer | ||
To define a proxy protocol when instantiating the IAM client. | https | Protocol | |
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 | |
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 the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. | String | ||
Set whether the IAM 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 IAM client should expect to load credentials through a profile credentials provider. | false | Boolean | |
Set whether the IAM client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume a IAM role for doing operations in IAM. | false | Boolean |