Migrating Spring Boot Applications to AWS Lambda - Thundra APM

Search…

Welcome to Thundra APM

Switch to Foresight Docs

Getting Started

Getting Started with Thundra APM

Quick Start Guide

Performance Benchmarks

Thundra Web Console

Functions List Page

Function Details Page

Invocation Detail Page

Applications Page

Applications Detail Page

Custom Dashboard Page

Architecture Page

Unique Traces Page

Unique Trace Details Page

Operations Page

API Details Page

Account & Settings

Error Inspector Page

Node.js

Integration Options for Node.js SDK

Integration Options for Node.js SDK in Containers and VMs

Configuration Options for Node.js

Enrich Tracing in Node.js

AWS Lambda Debugging for Serverless Node.js

TTD (Time Travel Debugging) for NodeJS

Node.js Example Projects

FAQ for Node.js SDK

Python

Integration Options for Python SDK

Configuration Options for Python

Enrich Tracing in Python

AWS Lambda Debugging for Serverless Python

Python Example Projects

FAQ for Python SDK

Java

Integration Options for Java SDK

Setting up Java SDK with Lambda Layer

Setting up Thundra Java Library manually

Setting up Java SDK with Serverless Framework

Setting up Java SDK with AWS SAM

Setting up Java SDK with AWS CDK

Setting up Java SDK as Lambda Container Image

Migrating Spring Boot Applications to AWS Lambda

Integration Options for Java SDK in Containers and VMs

Configuration Options for Java

Enrich Tracing in Java

AWS Lambda Debugging for Serverless Java

Java Example Projects

FAQ for Java SDK

Go

Integration Options for Go SDK

Configuration Options for Go

Enrich Tracing in Go

Golang Example Projects

.Net

Integration Options for .NET SDK

Integration Options for .NET SDK in Containers and VMs

Upgrading from v1.x to v2.x

Configuration Options for .NET SDK

Enrich Tracing in .NET

.NET Example Projects

FAQ for .NET SDK

Web Frameworks

Debugging

Time-Travel Debugging

AWS Lambda Debugger

IDE Integrations

IntelliJ IDEA Plugin

Observability

Root Cause Analysis of Outliers

Architectural View to Check The Issues at a Glance

Tracking Serverless Transactions End-to-End

Staying Aware of Issues with Alerts

How to Respond Alerts in Thundra

Reducing Data Size with Sampling

Chaos Engineering with Thundra

Three Pillars of Observability

Seamless Monitoring

Digging Observability Data with Thundra Queries

Performance

Zero Overhead with Lambda Extensions

Zero Overhead with Asynchronous Monitoring

Dealing with Cold Starts

Deployment Integrations

Serverless Framework

Step by Step Migration Guide from Epsagon to Thundra

Powered By GitBook

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:
​Packaging Executable for Maven​
​Packaging Executable for Gradle​
If you are using Docker, you can see the instructions for Lambda Container Images on this page:
Setting up Java SDK as Lambda Container Image
Adding Thundra APM
We recommend adding Thundra Agent as a Lambda Layer. You can see more about how to do this on this page:
Setting up Java SDK with Lambda Layer
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.ContainerHandler
Step 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.

Setting up Java SDK as Lambda Container Image

Integration Options for Java SDK in Containers and VMs

Last modified 9mo ago

Copy link

On this page

Creating a zipped Spring Boot Fat Jar

Adding Thundra APM

Thundra Integration and Necessary Configuration