The AWS Toolkit for Visual Studio Code allows you to work with your AWS Lambda functions in your local VS Code environment. With the AWS Toolkit, you can create, edit, test, debug, and deploy your Lambda functions, without having to leave the IDE. For detailed information about the AWS Lambda service, see the AWS Lambda Developer Guide.
The following sections describe how to get started working with Lambda functions in the AWS Toolkit for Visual Studio Code.
NoteIf you have already created Lambda functions by using the AWS Management Console, then you can invoke them from the Toolkit. Additionally, you can open your Lambda functions into VS Code from the AWS Lambda console, for additional information, see the AWS Lambda console to IDE topic in this user guide. To create a new Lambda function in VS Code, follow the steps outlined in the Creating a new serverless application (local) topic in this user guide.
PrerequisitesThe following conditions must be met to work with the AWS Lambda service in the AWS Toolkit.
The latest version of the AWS Toolkit for Visual Studio Code is installed and set up with your AWS credentials.
Your AWS Identity and Access Management (IAM) managed permissions and policies are configured to work with the AWS Lambda service. For detailed information on how to configure your permissions and create a compatible AWS managed policy, see the AWS Identity and Access Management for AWS Lambda topic in the AWS Lambda Developer Guide.
You have existing AWS Lambda functions or are familiar with how to create one. For instructions on how to create a Lambda function, see the Create your first Lambda function topic in the AWS Lambda Developer Guide.
To invoke a Lambda function from your AWS account into VS Code, complete the following steps.
From the AWS Toolkit for Visual Studio Code, expand the AWS explorer.
From the AWS explorer, expand Lambda to view your Lambda resources.
Open the context menu for (right-click) the Lambda function your want to invoke, then choose Invoke in the cloud or choose the Invoke in the cloud icon to open the Remote invoke configuration menu in VS Code.
From the Remote invoke configuration menu, specify your Payload settings and add any additional information that is required for the event.
NoteThe first invoke process may start running as soon as you choose Invoke in the cloud in the AWS explorer. The output is displayed in the OUTPUT tab of the VS Code terminal.
Choose the Remote Invoke button to invoke your function, The output is displayed in the OUTPUT tab of the VS Code terminal.
To delete a Lambda function, complete the following procedure.
WarningDo not use this procedure to delete Lambda functions that are associated with AWS CloudFormation. These functions must be deleted through your AWS CloudFormation stack.
From the AWS Toolkit for Visual Studio Code, expand the AWS explorer.
From the AWS explorer, expand Lambda to view your Lambda resources.
Right-click the Lambda function your want to delete, then choose Delete.
When prompted, confirm that you want to delete your function.
After the function is deleted, it's no longer listed in the AWS explorer.
Downloading a Lambda functionYou can download code from a remote Lambda function into your VS Code workspace for editing and debugging.
NoteTo download your Lambda function, you must be working in a VS Code workspace with an accessible folder and the AWS Toolkit only supports this feature with Lambda functions using Node.js and Python runtimes.
From the AWS Toolkit for Visual Studio Code, expand the AWS explorer.
From the AWS explorer, expand Lambda to view your Lambda resources.
Right-click the Lambda function your want to download, then choose Download.
Your Lambda function opens in the VS Code editor and displays in the AWS explorer when the download is complete. The AWS Toolkit also creates a launch configuration in the VS Code run panel allowing you to run and debug the Lambda function locally with AWS Serverless Application Model. For more information about using AWS SAM, see Running and debugging a serverless application from template (local).
You can deploy updates to new Lambda functions from an unspecified, temporary location on your local machine.
NoteWhen there are un-deployed changes to your lambda files, you're notified by the M icon located next to the modified files in the VS Code editor and in the AWS explorer.
Deploying from the VS Code editorOpen a file from your Lambda function in the VS Code editor, then make a change to the file.
Manually save from the VS Code main menu or pressing option+s (Mac) ctrl+s (Windows).
VS Code automatically prompts you about deploying your changes to the cloud, choose the Deploy button to confirm the deployment.
VS Code updates you on the status of your deployment and notifies you when the process is complete.
Open a file from your Lambda function in the VS Code editor, then make a change to the file.
From the AWS Toolkit, expand the AWS explorer.
From the AWS explorer, expand the AWS region with the Lambda function that you want to deploy changes for.
From the AWS region, expand Lambda and navigate the function that you want to deploy changes for.
From the quick menu next to your function, choose the Save and deploy your code icon.
VS Code updates you on the status of your deployment and notifies you when the process is complete.
The following procedures describe how to upload local changes made to your existing Lambda functions. This feature supports uploads with any Lambda supported runtime.
WarningBefore uploading your lambda function, be aware of the following:
Updating code in this way doesn't use the AWS SAM CLI for deployment or create an AWS CloudFormation stack
The AWS Toolkit doesn't validate code. Validate your code and test your function(s) before uploading any changes to the cloud.
From the AWS Toolkit for Visual Studio Code, expand the AWS explorer.
From the AWS explorer, expand Lambda to view your Lambda resources.
Right-click the Lambda function your want to upload your changes to, then choose Upload Lambda... to open the Select Upload Type menu.
Choose ZIP Archive to locate the ZIP Archive in your local directory.
When prompted, confirm the upload to start the upload of the selected ZIP Archive.
The status of your upload is displayed in VS Code and you're notified when the upload process is complete.
From the AWS Toolkit for Visual Studio Code, expand the AWS explorer.
From the AWS explorer, expand Lambda to view your Lambda resources.
Right-click the Lambda function your want to upload your changes to, then choose Upload Lambda... to open the Select Upload Type menu.
Choose Directory to proceed to the Build directory screen.
From the Build directory screen, choose No to choose a local directory for upload.
When prompted, confirm the upload to upload the selected directory.
The status of your upload is displayed in VS Code and you're notified when the upload process is complete.
Be aware of the following:
This procedure requires the AWS Serverless Application Model CLI.
The AWS Toolkit notifies you a matching handler can't be detected prior to upload.
To change the handler attached to your Lambda function, use the AWS Lambda console or the AWS Command Line Interface.
From the AWS Toolkit for Visual Studio Code, expand the AWS explorer.
From the AWS explorer, expand Lambda to view your Lambda resources.
Right-click the Lambda function your want to upload your changes to, then choose Upload Lambda... to open the Select Upload Type menu.
Choose Directory to proceed to the Build directory screen.
From the Build directory screen, choose Yes, then select a local directory for upload.
When prompted, confirm the upload to start building and uploading the selected directory.
The status of your upload is displayed in VS Code and you're notified when the upload process is complete.
To convert your Lambda function into an AWS SAM stack, complete the following steps.
WarningCurrently, only a subset of resources are supported when converting a Lambda function to an AWS SAM project. To locate any missing resources after a conversion, check the Lambda console and add them manually to your AWS SAM template. For additional details about supported and unsupported resources, see the Resource type support topic in the AWS CloudFormation Developer Guide.
From the AWS Toolkit, expand the AWS explorer.
From the AWS explorer, expand the AWS region with the Lambda function that you want to convert into an AWS SAM project.
From the AWS region, expand Lambda and navigate the function that you want to convert into an AWS SAM stack.
From the quick menu next to your Lambda function, choose the Convert to SAM Application icon to browse your local file system and specify a location for your new AWS SAM project.
After specifying a location the AWS Toolkit begins converting your Lambda function into an AWS SAM project, VS Code provides updates on the status of the process.
NoteThis process may take a few minutes.
When prompted by VS Code, enter a stack name, then press the Enter key to continue.
VS Code continues to update you with the status of your project, then notifies your when the process is complete and opens your new AWS SAM project as a VS Code workspace.
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