With the remote debugging feature in the AWS Toolkit for Visual Studio Code, you can debug your Lambda functions running directly in the AWS cloud. This is useful when investigating issues that are difficult to replicate locally or diagnose only with logs.
With remote debugging, you can:
Set breakpoints in your Lambda function code.
Step through code execution in real-time.
Inspect variables and state during runtime.
Debug Lambda functions deployed to AWS, including those in VPCs or with specific IAM permissions.
Remote debugging is supported for the following runtimes:
Python (AL2023)
Java
JavaScript/Node.js (AL2023)
Remote debugging is supported for both x86_64 and arm64 architectures.
Security and remote debuggingRemote debugging operates within existing Lambda security boundaries. Users can attach layers to a function using the UpdateFunctionConfiguration permission, which already has the ability to access function environment variables and configuration. Remote debugging doesn't extend beyond these existing permissions. Instead, it adds extra security controls through secure tunneling and automatic session management. Additionally, remote debugging is entirely a customer-controlled feature that requires explicit permissions and actions:
IoT Secure Tunnel Creation: The AWS Toolkit must create an IoT secure tunnel, which only occurs with the user's explicit permission using iot:OpenTunnel.
Debug Layer Attachment and Token Management: The debugging process maintains security through these controls:
The debugging layer must be attached to the Lambda function and this process requires the following permissions: lambda:UpdateFunctionConfiguration and lambda:GetLayerVersion.
A security token (generated via iot:OpenTunnel) must be updated in the function environment variable before each debug session, which also requires lambda:UpdateFunctionConfiguration.
For security, this token is automatically rotated and the debug layer is automatically removed at the end of each debug session and cannot be reused.
Remote debugging is supported for both x86_64 and arm64 architectures.
PrerequisitesBefore you begin remote debugging, ensure you have the following:
Remotely debug Lambda functionsFollow these steps to start a remote debugging session:
Open the AWS Explorer in VS Code by selecting the AWS icon in the left sidebar.
Expand the Lambda section to see your functions.
Right-click on the function you want to debug.
From the context menu, select Remotely invoke.
In the invoke window that opens, check the box for Enable debugging.
Click Invoke to start the remote debugging session.
Lambda functions have a 250MB combined limit for function code and all attached layers. The remote debugging layer adds approximately 40MB to your function's size.
A remote debugging session ends when you:
Choose Remove Debug Setup from the Remote invoke configuration screen.
Select the disconnect icon in the VS Code debugging controls.
Select the handler file in the VS Code editor.
The debug layer is automatically removed after 60 seconds of inactivity following your last invoke.
Disable remote debuggingThere are three ways to disable this feature:
Deny Function Updates: Set lambda:UpdateFunctionConfiguration to deny.
Restrict IoT Permissions: Deny IoT-related permissions
Block Debug Layers: Deny lambda:GetLayerVersion for the following ARNs:
arn:aws:lambda:*:*:layer:LDKLayerX86:*
arn:aws:lambda:*:*:layer:LDKLayerArm64:*
Disabling this feature prevents the debugging layer from being added during function configuration updates.
For more information on using Lambda in VS Code, refer to Developing Lambda functions locally with VS Code.
For detailed instructions on troubleshooting, advanced use cases, and region availability, see Remote debugging Lambda functions in the AWS Toolkit for Visual Studio Code User Guide.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4