Start online debug sessions while the AWS Lambda functions run on AWS Cloud. Thundra sets up an easy and secure connection between your AWS Lambda functions and VSCode. Debug your serverless applications natively with their own permissions. Stop mocking resources and simulating the environments! Put breakpoints and pause the execution of the NodeJS and Python functions to see the stack trace.
In order to use Serverless Debugger's VS Code extension, you need to complete all installation steps. Please follow the instructions below.
Install the extension from the marketplace
Edit VS Code and AWS Environment variables
- Open the Command Palette
(⇧⌘P) or (Ctrl + Shift + P)and select Thundra: Edit Configuration command.
VS Code Command Panel, select Thundra: Edit Configuration
- Paste the auth token to the
VS Code Configuration file, paste your
Edit AWS Environment variables
Go to your AWS Console and set your auth token value with the
THUNDRA_AGENT_LAMBDA_DEBUGGER_AUTH_TOKEN key as your environment variable.
If you need any help, please join our Discord channel and get personal help from the contributors.
How to use
After completing the installation steps, follow the guides below to start using Lambda Debugger.
Click on the “Start ServerlessDebugger Debugger” button on the Status Bar. You can also execute the command Thundra: Start Debugger to start the debugging session.
Set a breakpoint
Set a debug point on your VS Code. You can set multiple debug points as well.
Invoke your function
Now invoke your Lambda function to hit on the debug point. When there is a hit on your breakpoint the status bar below turns red.
You can start debugging when the variables and the call stack are loaded.
Debug session ends when your AWS Lambda function times out. You can update the timeout of your function for longer debug sessions.
ServerlessDebugger: Start Debuggerto start the debugger with the current profile's settings
ServerlessDebugger: Start Debugger (with a session name)to start the debugger with the given session name
ServerlessDebugger: Changeactive profile to change the active profile to the one given in your config file
ServerlessDebugger: Editconfiguration to edit the JSON file containing your debugger configuration
You can access all of the above commands from the command palette
(Cmd+Shift+P or Ctrl+Shift+P).
A self-hosted instance of the broker that provides the necessary functionality for online debugging can be installed on your own AWS account using our CloudFormation template or our CDK application. Please follow this guide to learn more.
Issues can be reported through the Thundra Debugger Issue Repository.