|
|
Today we announce the integration of Localstack in AWS Toolkit for the Visual Studio code that makes it easier for developers to test and tune applications without servers at local level. This improvement is based on our recent improvements to AWS Lambda development experiences, including a console to integrate IDE and remote tuning options that we launched in July 2025, and continues to simplify development without servers on Amazon Web Services (AWS).
When creating applications without servers, developers usually focus on three key areas to streamline their testing experience: testing units, testing integration and tuning in the cloud. Although the AWS command line interface provides the application model (AWS Sam Cli) excellent testing of local units for individual Lambda functions, developers working with architecture based on events that include multiple AWS services such as Amazon Simple Front Service (Amazon SQS) Integration testing. Although Localstack provided local AWS emulation, developers had to manage it as a separate tool, which required a comprehensive configuration and frequent switching of context between multiple interfaces, which slowed the development cycle.
Integration Localstack in AWS Toolkit for VS code
To deal with these challenges, we are introducing Localstack integration, so developers can connect the AWS Toolkit Pro VS code directly to Localstack’s endpoints. With this integration, developers can test and tune applications without servers without switching between tools or managing comprehensive Localstack settings. Developers can now imitate end-to-end workflows including services such as Lambda, Amazon SQS and EventBridge at local level without having to manage multiple tools, make complicated endpoint configurations, or deal with problems with the boundaries that previously required cloud resources.
The key advantage of this integration is that the AWS for VS code tools can now be connected to your own end points such as Localstack, something that was not possible before. Previously, in order to show the AWS Toolkit Pro VS code into its localstack environment, developers had to perform manual configuration and switching context between tools.
We start with Localstack in VS code is simple. Developers can start with Localstack Release A version that provides local AWS basic services ideal for developing and testing at an early stage. Using Wizarding in VS code, developers can install Localstack directly from the Toolkit interface that automatically installs Localstack extension and leads them through the setting process. When it is configured, developers can deploy applications without servers directly into the emulated environment and test their functions locally, all without abandoning their IDE.
Let’s try
First I update my copy of the AWS for VS code to the latest version. Once I did it, I see a new option when I go The creator of applications and click on The passage of the creator of applications. This allows me to install Localstack using a single click.
As soon as I finished the settings for Localstack, I can start it from the status bar, and then I can select Localstack from the list of my configured AWS profiles. On this illustration I use application composers to create simple architecture without servers using the Amazon API Gateway, Lambda and Dynamodb. I would normally put it in AWS using AWS SAM. In this case, I will use the same AWS SAM command to deploy my tray on a local level.
I’m just making `self -need – profile localstack ‘from the command line and watching the usual challenges. Localstack deployment with AWS SAM CLI provides exactly the same experience I am used to when deploying to AWS. In the screen image below, I see the standard output from AWS Sam and my new Localstack sources listed in the AWS Toolkit Explorer.
I can even go to the Lambda feature and edit the functional code that I put on locally!
On the Localstack website I can sign in and look at all the sources I ran locally. In the screen image below, you can see the local Dynamodb table that I just put on.
Improved development workflow
These new capabilities complement our recently running functions of the integration and remote console tuning on the IDE and create a comprehensive development experience that deals with various test needs during the life cycle. AWS Sam CLI provides excellent local testing for individual Lambda functions, efficiently handling scenarios of units testing. For integration testing, the integration of localstack allows multiservice working procedures locally without the complexity of AWS identity and access management (IAM), Amazon Virtual Private Cloud (AMAZON VPC), or service boundaries that can slow down speed.
If developers need to test with AWS services in development environments, they can use our remote tuning options that provide full access to Amazon VPC Resources and IAM roles. This graded approach liberates developers to focus on business logic during time -on -time Localstack, and then smoothly turns on cloud testing when it is necessary to verify against AWS behavior and configuration. Integration eliminates the need to switch between multiple tools and environments, so developers can identify and fix problems faster while maintaining flexibility in choosing the right test approach for their specific needs.
Now available
You can start using these new features via the AWS Toolkit for VS code updates to V3.74.0. Localstack integration is available in all AWS commercial regions except AWS Govcloud (USA) regions. If you want to learn more, visit the AWS Toolkit documentation for the VS code and Lambda documentation.
For developers who need wider service coverage or advanced abilities, Localstack offers additional levels with extended features. There are no additional AWS costs for using this integration.
These improvements are another significant step forward in our lasting commitment to simplify the development experience without a server. Over the last year, we have focused on the VS code to select a selection tool for developers without servers, and this integration of Localstack continues this path by providing tool developers for more efficiently creating and testing applications without servers than ever.