Speed up serverless testing with LocalStack integration in VS Code IDE

At present, we’re saying LocalStack integration within the AWS Toolkit for Visible Studio Code that makes it simpler than ever for builders to check and debug serverless purposes domestically. This enhancement builds upon our current enhancements to the AWS Lambda growth expertise, together with the console to IDE integration and distant debugging capabilities we launched in July 2025, persevering with our dedication to simplify serverless growth on Amazon Net Providers (AWS).

When constructing serverless purposes, builders usually concentrate on three key areas to streamline their testing expertise: unit testing, integration testing, and debugging assets working within the cloud. Though AWS Serverless Utility Mannequin Command Line Interface (AWS SAM CLI) supplies wonderful native unit testing capabilities for particular person Lambda features, builders working with event-driven architectures that contain a number of AWS providers, akin to Amazon Easy Queue Service (Amazon SQS), Amazon EventBridge, and Amazon DynamoDB, want a complete resolution for native integration testing. Though LocalStack offered native emulation of AWS providers, builders needed to beforehand handle it as a standalone software, requiring advanced configuration and frequent context switching between a number of interfaces, which slowed down the event cycle.

LocalStack integration in AWS Toolkit for VS Code
To deal with these challenges, we’re introducing LocalStack integration so builders can join AWS Toolkit for VS Code on to LocalStack endpoints. With this integration, builders can check and debug serverless purposes with out switching between instruments or managing advanced LocalStack setups. Builders can now emulate end-to-end event-driven workflows involving providers akin to Lambda, Amazon SQS, and EventBridge domestically, with no need to handle a number of instruments, carry out advanced endpoint configurations, or take care of service boundary points that beforehand required connecting to cloud assets.

The important thing advantage of this integration is that AWS Toolkit for VS Code can now hook up with customized endpoints akin to LocalStack, one thing that wasn’t attainable earlier than. Beforehand, to level AWS Toolkit for VS Code to their LocalStack atmosphere, builders needed to carry out handbook configuration and context switching between instruments.

Getting began with LocalStack in VS Code is simple. Builders can start with the LocalStack Free model, which supplies native emulation for core AWS providers excellent for early-stage growth and testing. Utilizing the guided software walkthrough in VS Code, builders can set up LocalStack instantly from the toolkit interface, which mechanically installs the LocalStack extension and guides them by way of the setup course of. When it’s configured, builders can deploy serverless purposes on to the emulated atmosphere and check their features domestically, all with out leaving their IDE.

Let’s attempt it out
First, I’ll replace my copy of the AWS Toolkit for VS Code to the most recent model. As soon as, I’ve completed this, I can see a brand new choice once I go to Utility Builder and click on on Walkthrough of Utility Builder. This permits me to put in LocalStack with a single click on.

As soon as I’ve accomplished the setup for LocalStack, I can begin it up from the standing bar after which I’ll be capable of choose LocalStack from the checklist of my configured AWS profiles. On this illustration, I’m utilizing Utility Composer to construct a easy serverless structure utilizing Amazon API Gateway, Lambda, and DynamoDB. Usually, I’d deploy this to AWS utilizing AWS SAM. On this case, I’m going to make use of the identical AWS SAM command to deploy my stack domestically.

I simply do `sam deploy –guided –profile localstack` from the command line and comply with the standard prompts. Deploying to LocalStack utilizing AWS SAM CLI supplies the very same expertise I’m used to when deploying to AWS. Within the screenshot under, I can see the usual output from AWS SAM, in addition to my new LocalStack assets listed within the AWS Toolkit Explorer.

I may even go in to a Lambda perform and edit the perform code I’ve deployed domestically!

Over on the LocalStack web site, I can login and check out all of the assets I’ve working domestically. Within the screenshot under, you possibly can see the native DynamoDB desk I simply deployed.

Enhanced growth workflow
These new capabilities complement our just lately launched console-to-IDE integration and distant debugging options, making a complete growth expertise that addresses completely different testing wants all through the event lifecycle. AWS SAM CLI supplies wonderful native testing for particular person Lambda features, dealing with unit testing situations successfully. For integration testing, the LocalStack integration permits testing of multiservice workflows domestically with out the complexity of AWS Identification and Entry Administration (IAM) permissions, Amazon Digital Personal Cloud (Amazon VPC) configurations, or service boundary points that may decelerate growth velocity.

When builders want to check utilizing AWS providers in growth environments, they’ll use our distant debugging capabilities, which offer full entry to Amazon VPC assets and IAM roles. This tiered method frees up builders to concentrate on enterprise logic throughout early growth phases utilizing LocalStack, then seamlessly transition to cloud-based testing when they should validate towards AWS service behaviors and configurations. The combination eliminates the necessity to swap between a number of instruments and environments, so builders can determine and repair points quicker whereas sustaining the flexibleness to decide on the suitable testing method for his or her particular wants.

Now accessible
You can begin utilizing these new options by way of the AWS Toolkit for VS Code by updating to v3.74.0. The LocalStack integration is accessible in all industrial AWS Areas besides AWS GovCloud (US) Areas. To be taught extra, go to the AWS Toolkit for VS Code and Lambda documentation.

For builders who want broader service protection or superior capabilities, LocalStack affords extra tiers with expanded options. There are not any extra prices from AWS for utilizing this integration.

These enhancements characterize one other vital step ahead in our ongoing dedication to simplifying the serverless growth expertise. Over the previous yr, we’ve targeted on making VS Code the software of selection for serverless builders, and this LocalStack integration continues that journey by offering instruments for builders to construct and check serverless purposes extra effectively than ever earlier than.