AWS Parameter Store
Since Camel 4.17
Only producer is supported
The AWS Parameter Store component supports AWS Systems Manager Parameter Store service.
Prerequisites
You must have a valid Amazon Web Services developer account, and be signed up to use Amazon Systems Manager Parameter Store. More information is available at AWS Systems Manager Parameter Store.
URI Format
aws-parameter-store://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 Parameter Store component supports 22 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
Component configuration. | ParameterStoreConfiguration | ||
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 | |
Required The operation to perform. Enum values:
| ParameterStoreOperations | ||
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 | ||
The region in which the SSM 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 | ||
Set whether the SSM client should expect to load credentials through a profile credentials provider. | 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 SSM client. | SsmClient | ||
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 SSM client. | String | ||
To define a proxy port when instantiating the SSM client. | Integer | ||
To define a proxy protocol when instantiating the SSM client. Enum values:
| HTTPS | Protocol | |
Amazon AWS Access Key. | 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 SSM 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 SSM 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 SSM. | false | boolean |
Endpoint Options
The AWS Parameter Store endpoint is configured using URI syntax:
aws-parameter-store:label
With the following path and query parameters:
Query Parameters (18 parameters)
| Name | Description | Default | Type |
|---|---|---|---|
Required The operation to perform. Enum values:
| ParameterStoreOperations | ||
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 | ||
The region in which the SSM 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 | ||
Set whether the SSM client should expect to load credentials through a profile credentials provider. | false | 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 | |
Autowired To use an existing configured AWS SSM client. | SsmClient | ||
To define a proxy host when instantiating the SSM client. | String | ||
To define a proxy port when instantiating the SSM client. | Integer | ||
To define a proxy protocol when instantiating the SSM client. Enum values:
| HTTPS | Protocol | |
Amazon AWS Access Key. | 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 SSM 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 SSM 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 SSM. | false | boolean |
Message Headers
The AWS Parameter Store component supports 14 message header(s), which is/are listed below:
| Name | Description | Default | Type |
|---|---|---|---|
CamelAwsParameterStoreOperation (producer) Constant: | The operation we want to perform. | String | |
CamelAwsParameterStoreMaxResults (producer) Constant: | The number of results to include in the response. | Integer | |
CamelAwsParameterStoreName (producer) Constant: | The name of the parameter. | String | |
CamelAwsParameterStoreNames (producer) Constant: | A comma separated list of parameter names. | String | |
CamelAwsParameterStoreDescription (producer) Constant: | The description of the parameter. | String | |
CamelAwsParameterStoreValue (producer) Constant: | The value of the parameter. | String | |
CamelAwsParameterStoreType (producer) Constant: | The type of the parameter (String, StringList, SecureString). | String | |
CamelAwsParameterStorePath (producer) Constant: | The hierarchy path for the parameter. | String | |
CamelAwsParameterStoreWithDecryption (producer) Constant: | Whether to decrypt SecureString values. | Boolean | |
CamelAwsParameterStoreRecursive (producer) Constant: | Whether to retrieve all parameters within a hierarchy recursively. | Boolean | |
CamelAwsParameterStoreOverwrite (producer) Constant: | Whether to overwrite an existing parameter. | Boolean | |
CamelAwsParameterStoreVersion (producer) Constant: | The version of the parameter. | Long | |
CamelAwsParameterStoreKmsKeyId (producer) Constant: | The KMS Key ID to use for SecureString encryption. | String | |
CamelAwsParameterStoreTier (producer) Constant: | The tier for the parameter (Standard, Advanced, Intelligent-Tiering). | String |
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
Using AWS Parameter Store Property Function
To use this function, you’ll need to provide credentials to AWS Systems Manager Parameter Store as environment variables:
export CAMEL_VAULT_AWS_ACCESS_KEY=accessKey
export CAMEL_VAULT_AWS_SECRET_KEY=secretKey
export CAMEL_VAULT_AWS_REGION=region You can also configure the credentials in the application.properties file such as:
camel.vault.aws.accessKey = accessKey
camel.vault.aws.secretKey = secretKey
camel.vault.aws.region = region | if you’re running the application on a Kubernetes based cloud platform, you can initialize the environment variables from a Secret or Configmap to enhance security. You can also enhance security by setting a Secret property placeholder which will be initialized at application runtime only. |
If you want instead to use the AWS default credentials provider, you’ll need to provide the following env variables:
export CAMEL_VAULT_AWS_USE_DEFAULT_CREDENTIALS_PROVIDER=true
export CAMEL_VAULT_AWS_REGION=region You can also configure the credentials in the application.properties file such as:
camel.vault.aws.defaultCredentialsProvider = true
camel.vault.aws.region = region It is also possible to specify a particular profile name for accessing AWS Parameter Store:
export CAMEL_VAULT_AWS_USE_PROFILE_CREDENTIALS_PROVIDER=true
export CAMEL_VAULT_AWS_PROFILE_NAME=test-account
export CAMEL_VAULT_AWS_REGION=region You can also configure the credentials in the application.properties file such as:
camel.vault.aws.profileCredentialsProvider = true
camel.vault.aws.profileName = test-account
camel.vault.aws.region = region camel.vault.aws configuration only applies to the AWS Parameter Store properties function (E.g when resolving properties). When using the operation option to create, get, list parameters etc., you should provide the usual options for connecting to AWS Services. |
At this point, you’ll be able to reference a property in the following way:
<camelContext>
<route>
<from uri="direct:start"/>
<to uri="{{aws-parameterstore:/myapp/config/endpoint}}"/>
</route>
</camelContext> Where /myapp/config/endpoint will be the name (path) of the parameter stored in the AWS Systems Manager Parameter Store.
You could specify a default value in case the parameter is not present on AWS Parameter Store:
<camelContext>
<route>
<from uri="direct:start"/>
<to uri="{{aws-parameterstore:/myapp/config/endpoint:http://localhost:8080}}"/>
</route>
</camelContext> In this case, if the parameter doesn’t exist, the property will fall back to "http://localhost:8080" as value.
Parameter Store Hierarchies
AWS Parameter Store supports hierarchical parameter names. You can organize parameters into hierarchies using forward slashes:
<camelContext>
<route>
<from uri="direct:start"/>
<log message="Database host is {{aws-parameterstore:/myapp/database/host}}"/>
<log message="Database port is {{aws-parameterstore:/myapp/database/port}}"/>
<log message="Database user is {{aws-parameterstore:/myapp/database/username}}"/>
</route>
</camelContext> SecureString Parameters
AWS Parameter Store supports SecureString parameters which are encrypted using AWS KMS. The Parameter Store properties function automatically decrypts SecureString parameters:
<camelContext>
<route>
<from uri="direct:start"/>
<log message="API Key is {{aws-parameterstore:/myapp/secrets/api-key}}"/>
</route>
</camelContext> The only requirement is adding the camel-aws-parameter-store jar to your Camel application.
Testing AWS Parameter Store Property Function with Localstack
For testing purpose you might want to test the function on Localstack. To make this easier you can use the following two properties in combination with the others:
camel.vault.aws.overrideEndpoint = true
camel.vault.aws.uriEndpointOverride = <localstack_url> With this you could be able to retrieve parameters with the function directly from the Localstack instance.
Parameter Store Producer operations
Camel-AWS-Parameter-Store component provides the following operation on the producer side:
-
getParameter
-
getParameters
-
getParametersByPath
-
putParameter
-
deleteParameter
-
deleteParameters
-
describeParameters
-
getParameterHistory
getParameter
This operation retrieves a single parameter value by name.
from("direct:getParameter")
.setHeader(ParameterStoreConstants.PARAMETER_NAME, constant("/myapp/config/endpoint"))
.to("aws-parameter-store://test?operation=getParameter"); getParameters
This operation retrieves multiple parameters by their names.
from("direct:getParameters")
.setHeader(ParameterStoreConstants.PARAMETER_NAMES, constant("/myapp/config/host,/myapp/config/port"))
.to("aws-parameter-store://test?operation=getParameters"); getParametersByPath
This operation retrieves all parameters within a hierarchy.
from("direct:getParametersByPath")
.setHeader(ParameterStoreConstants.PARAMETER_PATH, constant("/myapp/config"))
.setHeader(ParameterStoreConstants.RECURSIVE, constant(true))
.to("aws-parameter-store://test?operation=getParametersByPath"); putParameter
This operation creates or updates a parameter.
from("direct:putParameter")
.setHeader(ParameterStoreConstants.PARAMETER_NAME, constant("/myapp/config/endpoint"))
.setHeader(ParameterStoreConstants.PARAMETER_TYPE, constant("String"))
.setBody(constant("http://localhost:8080"))
.to("aws-parameter-store://test?operation=putParameter"); For SecureString parameters:
from("direct:putSecureParameter")
.setHeader(ParameterStoreConstants.PARAMETER_NAME, constant("/myapp/secrets/api-key"))
.setHeader(ParameterStoreConstants.PARAMETER_TYPE, constant("SecureString"))
.setBody(constant("my-secret-api-key"))
.to("aws-parameter-store://test?operation=putParameter"); deleteParameter
This operation deletes a single parameter.
from("direct:deleteParameter")
.setHeader(ParameterStoreConstants.PARAMETER_NAME, constant("/myapp/config/old-endpoint"))
.to("aws-parameter-store://test?operation=deleteParameter"); deleteParameters
This operation deletes multiple parameters.
from("direct:deleteParameters")
.setHeader(ParameterStoreConstants.PARAMETER_NAMES, constant("/myapp/config/old1,/myapp/config/old2"))
.to("aws-parameter-store://test?operation=deleteParameters"); Dependencies
Maven users will need to add the following dependency to their pom.xml.
pom.xml
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-aws-parameter-store</artifactId>
<version>${camel-version}</version>
</dependency> where ${camel-version} must be replaced by the actual version of Camel.
Spring Boot Auto-Configuration
When using aws-parameter-store 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-aws-parameter-store-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.