Thundra APM
Search…
Thundra Web Console
Node.js
Python
Java
Go
.Net
IDE Integrations
Observability
Performance
Deployment Integrations
Migrating Spring Boot Applications to AWS Lambda
Creating a zipped Spring Boot Fat Jar
To create a bootable jar file for Spring Boot Maven or Gradle, you can follow the instructions here:
If you are using Docker, you can see the instructions for Lambda Container Images on this page:
Adding Thundra APM
We recommend adding Thundra Agent as a Lambda Layer. You can see more about how to do this on this page:
Thundra Integration and Necessary Configuration
Required Steps
Step 1: Set your Lambda's runtime to
Custom Runtime Step 2: Set your Lambda's handler to
io.thundra.agent.container.springboot2.ContainerHandlerStep 3: Set the
THUNDRA_AGENT_LAMBDA_CONTAINER_SPRINGBOOT_APP_ARTIFACT environment variable to your application name, e.g. petclinic.jar. Important Note about Step 3
In this step, you must put your jar file into a separate zip file and upload that to AWS that way. Otherwise, if you upload the jar directly, AWS will extract the jar file itself which will break the integration.
Optional Steps
Step 4: Set the
THUNDRA_AGENT_LAMBDA_JVM_OPTIMIZEFORFASTSTARTUP environment variable to true . This is because we want the Lambda runtime JVM process to start with the configured VM arguments that are optimized for a fast start-up. See our documentation on this issue.Step 5: Set the
THUNDRA_AGENT_LAMBDA_REPORT_CLOUDWATCH_ENABLE environment variable to true . This is to report the collected telemetry data over AWS CloudWatch asynchronously. Beware that when you enable CloudWatch, you also have to set up the CloudWatch adapters. Make sure to checkout our documentation on this issue.Previous
Setting up Java SDK as Lambda Container Image
Next - Java
Integration Options for Java SDK in Containers and VMs
Last modified 1mo ago