【初心者向け】 LocalStackの概要と基本的な使い方について解説します
https://dev.classmethod.jp/articles/how-to-localstack/
#LocalStack
SQS-Admin is now available as native @localstack #extension omitting the necessity to launch additional containers to use #SQS-Admin.
Just integrated, just convenient.
⭐ if you like
Whilst working on the latest #OpenTelemetry Playground experiment I needed to find a way to set up an #S3 bucket whilst bringing up all the services. I came across a handy feature in #LocalStack called initialization hooks. You can run scripts at various stages of the LocalStack lifecycle: boot > start > ready > shutdown. In most cases, you want stuff to be at the "ready" stage 1/
A new experiment has landed in the OpenTelemetry Playground: https://buff.ly/hJbPOsH
This slightly convoluted example will use the AWS S3 exporter to store our telemetry data in blob storage. We spin up LocalStack to simulate S3 and use telemetrygen to generate test data.
SQS-Admin 0.7.0 is out 🎉
Highlight is
* the decreased #Docker image size from 20MB to 9MB
* app does no longer run as root
Queue management and interaction with #LocalStack made easy.
Dessa vez publiquei como faço a configuração da #AWS, tanto quando a empresa usa SSO, quanto quando uso #LocalStack. #bolhadev vocês também configuram assim?
https://eduardoklosowski.github.io/notes/dev/services/aws/index.html#cliente-cli
SQS-Admin 0.6.2 is out 🎉
With updated dependencies, new contributors, and nearly 60,000 downloads.
Queue management and interaction with #LocalStack made easy.
Ei #bolhaDev, vocês usam #AWS? #LocalStack? Publiquei minhas notas de como uso ele no #docker compose.
https://eduardoklosowski.github.io/notes/dev/services/aws/index.html#localstack
【AWS】Localstack CLIを利用して、ローカル環境にAWSリソースを生やして利用する！
https://qiita.com/suiwave/items/1d2ef0614efa23d5a740?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
The next article to be taken out from Medium is ... The StaCo App! This article has a story but I'll tell about it only sometime in the future. It tells how to use #localstack and use #kotlin to leverage services creation with #spring in the #jvm. joaofilipesabinoesperancinha.nl/blog/blog0-1...
Learning AWS with Localstack a...
The next article to be taken out from Medium is ... The StaCo App! This article has a story but I'll tell about it only sometime in the future. It tells how to use #localstack and use #kotlin to leverage services creation with #spring in the #jvm. https://joaofilipesabinoesperancinha.nl/blog/blog0-11-staco
This is a repost of one of the first videos I created for YouTube when I felt a lot shyer than currently. So much so that I could only dare to post a walkthrough without even talking. This video shows how to work with #localstack, #kotlin and #spring on @dailymotion.com.web.brid.gy : https://dai.ly/x98uhdc
Today’s adventure started hopeful. I managed to get the #Uppy Webcam plugin mostly working across Web, Android, and iOS; and then my #LocalStack S3 bucket dumped its CORS configuration so my #Tailscale funnel that I use to expose my local #Rails server to the #TurboNative apps got rejected.
But before I reapplied the CORS config I tried to update the `is-mobile` package for some reason and now even after reverting and nuking `node_modules` Uppy Webcam doesn’t want to use the Android native webcam anymore and I have no idea why
😭😭😭
A problem often neglected when it comes to choosing #cloud infrastructure over self-hosted is the often inevitable loss of test coverage.
I'm currently working on a project involving deep graphs, and the management has been toying with the idea of migrating the data model from a vanilla MySQL to a graph db like #Neptune over #AWS.
The data model and storage layer are usually the most crucial parts in any piece of software, and that's where you want your integration tests coverage to catch all the possible corner cases.
But where do you even start to write CI tests for a service that is cloud-only?
It's quite straightforward with MySQL. You just spawn a MySQL container with #TestContainers from your code, and you've basically got an exact replica of the storage infrastructure that you'll be using wherever your software runs.
But what about a service like Neptune?
If you're lucky and you're using a popular cloud service, then #LocalStack may probably provide you with a reliably similar replica of that service that you can run locally, and instruct your tests to spawn before running.
But more niche services, or services like Neptune that take a heavy toll on memory, aren't usually provided by LocalStack.
So what do you do? Create a test AWS account to be used only by your integration tests? And face the nightmare of how to properly secure it in a context where anybody with the source code can run stuff on your cloud infrastructure without authentication?
And how about the costs, since every request is diligently billed, even if it comes from your own integration tests? As your team size scales up and the number of pull requests, CI pipelines and local test runs increases what do you do? Ask them to run test suites only when really required in order to save money?
Any modern piece of software infrastructure must also provide developers with the ability to have a local replica that they can reliably use to test things out. Products like LocalStack shouldn't be an afterthought developed by 3rd-party companies or volunteers. We can argue if we prefer a cloud-first or local-first infrastructure, sure. But a cloud-only infrastructure is a guarantee of poorer test coverage, poorer developer experience, and probably more unstable code.
@programming.a.gup.pe
I'm currently working on a project involving deep graphs, and the management has been toying with the idea of migrating the data model from a vanilla MySQL to a graph db like #Neptune over #AWS.
The data model and storage layer are usually the most crucial parts in any piece of software, and that's where you want your integration tests coverage to catch all the possible corner cases.
But where do you even start to write CI tests for a service that is cloud-only?
It's quite straightforward with MySQL. You just spawn a MySQL container with #TestContainers from your code, and you've basically got an exact replica of the storage infrastructure that you'll be using wherever your software runs.
But what about a service like Neptune?
If you're lucky and you're using a popular cloud service, then #LocalStack may probably provide you with a reliably similar replica of that service that you can run locally, and instruct your tests to spawn before running.
But more niche services, or services like Neptune that take a heavy toll on memory, aren't usually provided by LocalStack.
So what do you do? Create a test AWS account to be used only by your integration tests? And face the nightmare of how to properly secure it in a context where anybody with the source code can run stuff on your cloud infrastructure without authentication?
And how about the costs, since every request is diligently billed, even if it comes from your own integration tests? As your team size scales up and the number of pull requests, CI pipelines and local test runs increases what do you do? Ask them to run test suites only when really required in order to save money?
Any modern piece of software infrastructure must also provide developers with the ability to have a local replica that they can reliably use to test things out. Products like LocalStack shouldn't be an afterthought developed by 3rd-party companies or volunteers. We can argue if we prefer a cloud-first or local-first infrastructure, sure. But a cloud-only infrastructure is a guarantee of poorer test coverage, poorer developer experience, and probably more unstable code.
@programming.a.gup.pe
> How To Make #AWS Not Suck
> In this #fireship #youtube #video you're going to learn how to make #cloudComputing great again
#pulumi and #sst are really cool #infrastructure as #code tools
#localStack is a full #cloud environment that runs in #docker.
#cloudcraft by #datadog let's you visualize your #cloud resources
#encore is an opinionated #backend #iac #framework
https://www.youtube.com/watch?v=gJmz31JywM0
#terraform #typescript #javaScript #webDev #serverless #nextjs #svelte #vercel #web #dev
📦 #LocalStack 3.7 Released: Local #AWS Emulator
• 🛠️ Emulates 50+ #AWS services locally (#Lambda, #S3, #DynamoDB, #Kinesis, #SQS, #SNS, more)
• 🐳 Runs in a single #Docker container on your machine or #CI environment
• 💻 Enables local #CloudDevelopment without connecting to remote cloud
• 🧪 Ideal for testing complex #CDK applications or #Terraform configurations
• 🔧 Supports additional features like #CloudDevelopment workflows
• 🆓 Open-source version available, with extended Pro version
#LocalStack provides a comprehensive local #AWS environment for developers and testers, simplifying cloud application development and reducing costs. Compatible with various deployment methods including CLI, Docker, and Helm.
So #localstack just broke the default configuration of 3.x < 3.7.0, including our CI.
When localstack spins up, it pulls the LetEncrypt SSL cert and private key for localhost.localstack.cloud from https://github.com/localstack/localstack-artifacts/tree/master/local-certs/server.key; there was a bot that updated that cert monthly to keep it from expiring
As of 3.7.0 I guess they don't do that anymore, and they *removed the cert/key* from the repo. So now all older versions fail at startup.
:picardfacepalm:
LocalStack に入門するべく 「LocalStack 実践入門 | AWS アプリケーション開発ワークショップ」をやってみた
https://dev.classmethod.jp/articles/getting-started-with-localstack-hands-on-aws-app-development-workshop/
#localstack as a "free" tool. The free code works fine for integration testing a few specific #AWS services or a few app that happen to be all community edition services.
But for any real world app that wasn't architected specifically to stay within localstack's free offering, using local stack for an entire app requires Pro & a monthly subscription.
Search for "(pro)"
https://docs.localstack.cloud/user-guide/aws/feature-coverage/
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst