AWS Database Migration Service provides migration solutions from databases, data warehouses, and other types of data stores (e.g. S3, SAP). The migration can be homogeneous (source and target have the same type), but often is heterogeneous as it supports migration from various sources to various targets (self-hosted and AWS services). LocalStack supports DMS with selected use cases. In this session from LocalStack Community Meetup July '24, Mathieu Cloutier explores how to use LocalStack to migrate from a MariaDB database to an AWS Kinesis Stream. He goes over the differences between CDC and full load, and as a bonus you will see how easy it is to migrate from an external database to your Kinesis Stream — tested all on your local machine!

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.