thundra_agent_lambda_debugger_auth_token
environment variable.Thundra: Change local root
command in the menu and point to your build folder where you keep your .js
and .js.map
files. "rootDir": "."
in your .tsconfig
file should compile your files to match the folder structure. src/api/hello.ts
file, AWS Lambda will put the compiled code under src/api/hello.js
and specifying the root directory in your .tsconfig
will compile your code under, let's say build/src/api/hello.js
. ./build
, you are ready to start debugging your function.keepOutputDirectory: true
to upload your source files to the remote and match your local setup with it to start debugging.thundra_agent_lambda_debugger_auth_token
environment variable to the authentication token that you receive from the Thundra console. By doing this, Thundra will start your function in debug mode and you will be able to connect your function from your IDE to start the debugging session.thundra_agent_lambda_debugger_enable
environment variable to false. This ensures that even if you have thundra_agent_lambda_debugger_auth_token
, AWS Lambda Debugging will still be disabled.default
. If you want to use another session name, you can specify it using the thundra_agent_lambda_debugger_session_name
environment variable.thundra_agent_lambda_debugger_broker_host
environment variable to reduce latency during a debugging session.thundra_agent_lambda_debugger_auth_token
thundra_agent_lambda_debugger_session_name
thundra_agent_lambda_debugger_broker_host
debug.thundra.io
.thundra_agent_lambda_debugger_broker_host
thundra_agent_lambda_debugger_wait_max
thundra_agent_lambda_debugger_logs_enable
thundra_agent_lambda_debugger_enable