AWS Toolkit for Visual Studio CodeThe AWS Toolkit for Visual Studio Code (VS Code), or simply the Toolkit, is an extension that enables you to interact with certain services of Amazon Web Services (AWS) from within the VS Code editor. The following screenshots show important parts of the Toolkit. Fundamental UI ComponentsThe AWS ExplorerThe CDK ExplorerAWS Commands in the Command PaletteContents{ Return to Top } Feature OverviewYou can use the AWS Toolkit for VS Code to interact with several AWS resources in various ways. These include the following:
See Features below for high-level details, or jump right into the AWS Toolkit for Visual Studio Code User Guide. { Return to Contents } or { Return to Top } SetupTo access most features of the AWS Toolkit for VS Code, you must complete the steps defined in the Setting Up topic of the user guide. These steps include the following:
To use the Toolkit to develop serverless applications with AWS, you must also set up your toolchain and do the following on the local machine where the Toolkit is installed:
For complete setup instructions for these three components, see Installing the AWS SAM CLI in the AWS Serverless Application Model (AWS SAM) Developer Guide. { Return to Contents } or { Return to Top } Features
{ Return to Contents } or { Return to Top } Serverless Applications, Lambda Functions, and CloudFormation StacksThe AWS Toolkit for VS Code enables you to develop AWS serverless applications locally. It also enables you to do the following through the AWS Explorer:
The following example shows a highlight of this functionality. After you have created a serverless application, you can locally run, debug, and further develop that application in the VS Code editor. For example: Take special note of the CodeLenses that enable you to run and debug the application locally. The status and results are shown in the OUTPUT panel when the AWS Toolkit output channel is selected. When you're satisfied, you can deploy your application to a CloudFormation stack and then run the Lambda function on AWS. For full details, see the AWS Explorer in the Toolkit's user guide. Additional Information about CodeLensesThe functions that have Codelenses are those that use AWS Lambda-function handler syntax. A handler is a function that Lambda calls to start execution of a Lambda function. These CodeLenses enable you to locally run or debug the corresponding serverless application. CodeLens actions in the Toolkit include:
{ Return to Features } or { Return to Top } AWS CDK ApplicationsThe AWS Toolkit for VS Code enables you to work with AWS Cloud Development Kit (AWS CDK) applications. Using the CDK Explorer on the Toolkit, you can view CDK applications within your Workspace that have been synthesized. Example: For full details, see the CDK Explorer in the Toolkit's user guide. { Return to Features } or { Return to Top } Amazon EventBridge SchemasThe AWS Toolkit for VS Code provides support for Amazon EventBridge schemas. Using the AWS Explorer of the Toolkit, you can perform the following operations on these schemas:
Example: For full details, see Working with Amazon EventBridge Schemas in the Toolkit's user guide. { Return to Features } or { Return to Top } Amazon ECS Task Definition FilesThe AWS Toolkit for VS Code provides support for Amazon Elastic Container Service (Amazon ECS). With the Toolkit installed in VS Code, IntelliSense functionality is provided for Amazon ECS task-definition files that you are updating in the editor. Example: For full details, see Working with Amazon Elastic Container Service in the Toolkit's user guide. { Return to Features } or { Return to Top } Appendix A: AWS CommandsThe AWS Toolkit for VS Code has several features that you can access through the Command Palette (select View, then Command Palette):
{ Return to Contents } or { Return to Top } Appendix B: Get HelpFor additional details on how to use the AWS Toolkit for VS Code, see the user guide. To report issues with the Toolkit or to propose Toolkit code changes, see the aws/aws-toolkit-vscode repository on GitHub. You can also contact AWS directly. { Return to Contents } or { Return to Top } |