具有多个 lambda 端点的 Spring Boot + Apache Camel + AWS Lambda

Question

I am learning Apache Camel and how to use it with Spring Boot. I have been able to successfully hit one lambda function using Camel and Spring and so far it works great. However I'm having trouble when I try to add a second function that I want to hit using a different route.

At a core, the problem I'm having is that it seems Camel requires that the property camel.component.aws-lambda.configuration.function is defined in order to create an endpoint. But obviously I don't want to define that property because I need to have multiple functions, not just a single one.

Current code that works:

application.yaml:

camel:
  component:
    aws-lambda:
      configuration:
        access-key: myAccessKey
        secret-key: mySecretKey
        region: MY_REGION
        function: myFunction
        operation: invokeFunction

My route:

@Component
public class MessageTestInvocationRoute extends RouteBuilder {

    @Override
    public void configure() throws Exception {
        from("somewhere").routeId("lambda")
                .to("aws-lambda://myFunction");
    }
}

Now how can I add a second route? As soon as I comment out the camel.component.aws-lambda.configuration.function property, my existing route breaks due to an NPE. But if I leave that property defined, then it seems all AWS calls will be tied to that one function.

I have tried looking into making custom LambdaComponent s, I have tried looking into making custom AWSLambdaClient s, none of these did anything useful - it all falls apart as soon as I comment out that property.

Answer 1

I figured it out. The reason I was getting an NPE is because I did not have an operation defined. When the function and operation are defined in application.yaml , then Spring attempts to use that one, which is why commenting out those properties caused that issue. The solution was to comment out the function and operation properties, and then change my route code to:

@Component
public class MessageTestInvocationRoute extends RouteBuilder {

    @Override
    public void configure() throws Exception {
        from("somewhere").routeId("lambda")
                .to("aws-lambda://myFunction?operation=invokeFunction");
    }
}

Now I am able to create multiple routes that all function just fine in parallel.