When it comes to productivity, developer experience is more than just a buzzword. Creating an intuitive developer experience could help you get more out of LocalStack by democratizing access, cutting out manual tasks, and making environments more easily interchangeable between LocalStack and AWS. On a day-to-day basis, this could mean fewer tickets, less time spent creating environments, and more time on the important work that your environments support. This demo session will show how LocalStack’s new integration with Quali Torque can accelerate deployment on both LocalStack and AWS by using generative AI to create reusable environment templates that can be deployed to LocalStack and AWS interchangeably in just a few clicks, providing a self-service catalog for your teams to find and provision environments quickly and easily without access to create or modify resource configurations, simplifying the deployment experience by eliminating complexity and security requirements to run environments on AWS, and tracking all activity to identify performance issues for LocalStack deployments and wasted cloud costs for AWS deployments proactively.

Connecting your applications to LocalStack has not always been easy. In this video, Simon from the LocalStack team discusses how we streamlined the LocalStack networking experience. We discussed the challenges of connecting your applications to LocalStack and how we're simplifying the LocalStack networking experience. Simon also discussed about configurations required for more complex networking setups, and some common networking scenarios, with example configuration for achieving connectivity.

LocalStack integrates with official AWS Software Development Kits (SDKs) so you can connect to LocalStack services using the same application code you use for AWS services. This lets you develop and test your applications locally without connecting to the cloud. In this video, we will talk about how you can connect to LocalStack emulated services using AWS SDKs.

LocalStack is ephemeral, so when you stop and restart it, all data is lost. You can use certain features to save the state & load it back when you restart LocalStack. This includes saving the local state for S3 buckets, DynamoDB tables, RDS databases and more. In this video, we explore three mechanisms that allow you to save state in LocalStack: persistence, state export and import, and Cloud Pods.