THUNDRA_AGENT_LAMBDA_DEBUGGER_AUTH_TOKEN
environment variable.Custom runtime
.AWS_LAMBDA_EXEC_WRAPPER
environment variable to /opt/thundra_wrapper
62
or higher.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
, online debugging will be still disabled.default
.” If you want to use another session name, you can specify it using the THUNDRA_AGENT_LAMBDA_DEBUGGER_SESSION_NAME
environment variable.Oregon
by default, but we also support different broker hosts (listed below). You can select a broker host and set it to the 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
default
."THUNDRA_AGENT_LAMBDA_DEBUGGER_BROKER_HOST
debug.thundra.io
."THUNDRA_AGENT_LAMBDA_DEBUGGER_BROKER_PORT
444
.THUNDRA_AGENT_LAMBDA_DEBUGGER_WAIT_MAX
60000
.THUNDRA_AGENT_LAMBDA_DEBUGGER_LOGS_ENABLE
false
.THUNDRA_AGENT_LAMBDA_DEBUGGER_ENABLE
true
to enable the debugger (the authentication token environment variable should also be set), and it can be set to false
to disable the Thundra debugger.