Skip to content
Core Spring Framework support for AWS Lambda functions (in Java)
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
example Move handler resolution into constructor Nov 28, 2016
gradle/wrapper Initial commit Jul 13, 2016
.gitignore Initial commit Jul 13, 2016
.travis.yml Add .travis.yml Jul 19, 2016
LICENSE Initial commit Jul 13, 2016 Bump version Nov 28, 2016
build.gradle Initial commit Jul 13, 2016 Add publish to Maven Central Jul 21, 2016
gradlew Initial commit Jul 13, 2016
gradlew.bat Initial commit Jul 13, 2016
settings.gradle Initial commit Jul 13, 2016


Build Status Maven Central

A Java library to enable core Spring Framework dependency injection support and eliminate some boilerplate around AWS Lambda.


When using Java with AWS Lambda, AWS requires you to either implement one of their base interfaces (RequestHandler or RequestStreamHandler), or provide a class with a single method handle(T input, Context context). This library leverages the interface-based approach. When deploying the function, you need to point Lambda to your "main handler" class, which serves as the entry point to your application.

The main usage is simple: import this library as a dependency and extend one of the main abstract classes in as your main handler class. You will be forced to implement the getApplicationContext method, which is where you will provide the instance to your Spring application context class, which will be used throughout the rest of the application.

Once you have provided an ApplicationContext, you can use Spring's dependency injection features anywhere besides in your MainHandler class. This means you can take the annotation driven approach, use autowiring, etc.

The abstract handler classes in this library actually use the provided ApplicationContext instance to find a bean of type RequestHandler (Lambda's main interface) and call it's handleRequest method, so most of your application logic should not be in your MainHandler class, but rather in a separate bean of type RequestHandler.

The main pattern I recommend is creating a fairly empty MainHandler class that implements one of this library's interfaces, supplies an ApplicationContext, and then does nothing else. Additionally, you create another implementation of RequestHandler and register it as a bean (either manually in your Spring configuration or using annotations such as @Component). This custom RequestHandler can then take advantage of all of Spring's dependency injection tools. You are free to implement your application logic in there, or split it out over several, loosely coupled classes, using Spring dependency injection to wire it all together.

See the example directory for some a simple example of this pattern.

If you have any questions/comments/issues, please feel free to use the GitHub issue tracker to report them.

Best, /cc

Dependency Information

Found on Maven Central (


compile 'me.ccampo:spring-aws-lambda:1.1.0'




To Build:

For -nix and OSX:

./gradlew build

For Windows:

gradlew.bat build

Requires Java 1.8

You can’t perform that action at this time.