AWS Lambda
Since Camel 3.2
Only producer is supported
The AWS2 Lambda component supports create, get, list, delete and invoke AWS Lambda functions.
Prerequisites
You must have a valid Amazon Web Services developer account, and be signed up to use Amazon Lambda. More information is available at AWS Lambda.
When creating a Lambda function, you need to specify a IAM role which has at least the AWSLambdaBasicExecuteRole policy attached.
URI Format
aws2-lambda://functionName[?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
The component level is the highest level which holds general and common configurations that are inherited by the endpoints. 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.
Configuring components can be done with the Component DSL, in a configuration file (application.properties|yaml), or directly with Java code.
Configuring Endpoint Options
Where you find yourself configuring the most is on endpoints, as endpoints often have many options, which allows you to configure what you need the endpoint to do. The options are also categorized into whether the endpoint is used as consumer (from) or as a producer (to), or used for 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, which allows to not hardcode urls, port numbers, sensitive information, and other settings. In other words placeholders allows to externalize the configuration from your code, and gives more flexibility and reuse.
The following two sections lists all the options, firstly for the component followed by the endpoint.
Component Options
The AWS Lambda component supports 16 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
Component configuration. |
Lambda2Configuration |
||
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. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction. Enum values:
|
invokeFunction |
Lambda2Operations |
|
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 |
|
The region in which Lambda 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 |
||
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 Lambda client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. |
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 a existing configured AwsLambdaClient as client. |
LambdaClient |
||
To define a proxy host when instantiating the Lambda client. |
String |
||
To define a proxy port when instantiating the Lambda client. |
Integer |
||
To define a proxy protocol when instantiating the Lambda client. Enum values:
|
HTTPS |
Protocol |
|
Amazon AWS Access Key. |
String |
||
Amazon AWS Secret Key. |
String |
Endpoint Options
The AWS Lambda endpoint is configured using URI syntax:
aws2-lambda:function
with the following path and query parameters:
Query Parameters (14 parameters)
Name | Description | Default | Type |
---|---|---|---|
The operation to perform. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction. Enum values:
|
invokeFunction |
Lambda2Operations |
|
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 |
|
The region in which Lambda 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 |
||
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 Lambda client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. |
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 a existing configured AwsLambdaClient as client. |
LambdaClient |
||
To define a proxy host when instantiating the Lambda client. |
String |
||
To define a proxy port when instantiating the Lambda client. |
Integer |
||
To define a proxy protocol when instantiating the Lambda client. Enum values:
|
HTTPS |
Protocol |
|
Amazon AWS Access Key. |
String |
||
Amazon AWS Secret Key. |
String |
Required Lambda component options
You have to provide the awsLambdaClient in the Registry or your accessKey and secretKey to access the Amazon Lambda 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
The AWS Lambda component supports 30 message header(s), which is/are listed below:
Name | Description | Default | Type |
---|---|---|---|
Constant: |
Required The operation we want to perform. Override operation passed as query parameter. |
String |
|
CamelAwsLambdaS3Bucket (createFunction) Constant: |
Amazon S3 bucket name where the .zip file containing your deployment package is stored. This bucket must reside in the same AWS region where you are creating the Lambda function. |
String |
|
CamelAwsLambdaS3Key (createFunction) Constant: |
The Amazon S3 object (the deployment package) key name you want to upload. |
String |
|
CamelAwsLambdaS3ObjectVersion (createFunction) Constant: |
The Amazon S3 object (the deployment package) version you want to upload. |
String |
|
CamelAwsLambdaZipFile (createFunction) Constant: |
The local path of the zip file (the deployment package). Content of zip file can also be put in Message body. |
String |
|
CamelAwsLambdaDescription (createFunction) Constant: |
The user-provided description. |
String |
|
CamelAwsLambdaRole (createFunction) Constant: |
Required The Amazon Resource Name (ARN) of the IAM role that Lambda assumes when it executes your function to access any other Amazon Web Services (AWS) resources. |
String |
|
CamelAwsLambdaRuntime (createFunction) Constant: |
Required The runtime environment for the Lambda function you are uploading. (nodejs, nodejs4.3, nodejs6.10, java8, python2.7, python3.6, dotnetcore1.0, odejs4.3-edge). |
String |
|
CamelAwsLambdaHandler (createFunction) Constant: |
Required The function within your code that Lambda calls to begin execution. For Node.js, it is the module-name.export value in your function. For Java, it can be package.class-name::handler or package.class-name. |
String |
|
CamelAwsLambdaTargetArn (createFunction) Constant: |
The parent object that contains the target ARN (Amazon Resource Name) of an Amazon SQS queue or Amazon SNS topic. |
String |
|
CamelAwsLambdaMemorySize (createFunction) Constant: |
The memory size, in MB, you configured for the function. Must be a multiple of 64 MB. |
Integer |
|
CamelAwsLambdaKMSKeyArn (createFunction) Constant: |
The Amazon Resource Name (ARN) of the KMS key used to encrypt your function’s environment variables. If not provided, AWS Lambda will use a default service key. |
String |
|
CamelAwsLambdaEnvironmentVariables (createFunction) Constant: |
The key-value pairs that represent your environment’s configuration settings. |
Map |
|
CamelAwsLambdaPublish (createFunction updateFunction) Constant: |
This boolean parameter can be used to request AWS Lambda to create the Lambda function and publish a version as an atomic operation. |
Boolean |
|
CamelAwsLambdaTimeout (createFunction) Constant: |
The function execution time at which Lambda should terminate the function. The default is 3 seconds. |
Integer |
|
CamelAwsLambdaTags (createFunction) Constant: |
The list of tags (key-value pairs) assigned to the new function. |
Map |
|
CamelAwsLambdaTracingConfig (createFunction) Constant: |
Your function’s tracing settings (Active or PassThrough). |
String |
|
CamelAwsLambdaSecurityGroupIds (createFunction) Constant: |
If your Lambda function accesses resources in a VPC, a list of one or more security groups IDs in your VPC. |
List |
|
CamelAwsLambdaSubnetIds (createFunction) Constant: |
If your Lambda function accesses resources in a VPC, a list of one or more subnet IDs in your VPC. |
List |
|
CamelAwsLambdaEventSourceArn (createEventSourceMapping) Constant: |
The Amazon Resource Name (ARN) of the event source. |
String |
|
CamelAwsLambdaEventSourceBatchSize (createEventSourceMapping) Constant: |
The maximum number of records in each batch that Lambda pulls from your stream or queue and sends to your function. |
Integer |
|
CamelAwsLambdaEventSourceUuid (deleteEventSourceMapping) Constant: |
The identifier of the event source mapping. |
String |
|
CamelAwsLambdaResourceArn (listTags tagResource untagResource) Constant: |
The function’s Amazon Resource Name (ARN). |
String |
|
CamelAwsLambdaResourceTags (tagResource) Constant: |
A list of tags to apply to the function. |
Map |
|
CamelAwsLambdaResourceTagKeys (untagResource) Constant: |
A list of tag keys to remove from the function. |
List |
|
CamelAwsLambdaVersionDescription (publishVersion) Constant: |
A description for the version to override the description in the function configuration. |
String |
|
CamelAwsLambdaVersionRevisionId (publishVersion) Constant: |
Only update the function if the revision ID matches the ID that’s specified. |
String |
|
CamelAwsLambdaFunctionVersion (createAlias listAliases) Constant: |
The function version to set in the alias. |
String |
|
CamelAwsLambdaAliasFunctionName (createAlias deleteAlias getAlias) Constant: |
Required The function name of the alias. |
String |
|
CamelAwsLambdaAliasFunctionDescription (createAlias) Constant: |
The function description to set in the alias. |
String |
List of Available Operations
-
listFunctions
-
getFunction
-
createFunction
-
deleteFunction
-
invokeFunction
-
updateFunction
-
createEventSourceMapping
-
deleteEventSourceMapping
-
listEventSourceMapping
-
listTags
-
tagResource
-
untagResource
-
publishVersion
-
listVersions
-
createAlias
-
deleteAlias
-
getAlias
-
listAliases
Examples
Producer Example
To have a full understanding of how the component works, you may have a look at these integration tests
Producer Examples
-
CreateFunction: this operation will create a function for you in AWS Lambda
from("direct:createFunction").to("aws2-lambda://GetHelloWithName?operation=createFunction").to("mock:result");
and by sending
template.send("direct:createFunction", ExchangePattern.InOut, new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(Lambda2Constants.RUNTIME, "nodejs6.10");
exchange.getIn().setHeader(Lambda2Constants.HANDLER, "GetHelloWithName.handler");
exchange.getIn().setHeader(Lambda2Constants.DESCRIPTION, "Hello with node.js on Lambda");
exchange.getIn().setHeader(Lambda2Constants.ROLE,
"arn:aws:iam::643534317684:role/lambda-execution-role");
ClassLoader classLoader = getClass().getClassLoader();
File file = new File(
classLoader
.getResource("org/apache/camel/component/aws2/lambda/function/node/GetHelloWithName.zip")
.getFile());
FileInputStream inputStream = new FileInputStream(file);
exchange.getIn().setBody(inputStream);
}
});
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 Lambda there are multiple operations you can submit, as an example for Get Function request, you can do something like:
from("direct:getFunction")
.setBody(GetFunctionRequest.builder().functionName("test").build())
.to("aws2-lambda://GetHelloWithName?awsLambdaClient=#awsLambdaClient&operation=getFunction&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-lambda</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-lambda 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-lambda-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.