[operator_nil]

This is exactly what I was waiting for.

Although I love localstack and am grateful for what they have done, I always thought that an open community-driven solution would be much more suitable and opens a lot of doors for AWS engineers to contribute back. I’m certain that it’s on their best interest to do so (specially as many of their popular products have local versions)

It’s a no-brainer to me as AI adoption continues to increase: local-first integration testing is a must and teams that are equipped to do so will be ahead of everyone else

[drzaiusx11]

How is it in AWS' best interest to provide support or changes for a FOSS clone (albeit with ephemeral storage)? I believe that providing locked down local-first containers themselves for various services (which they do for services like ddb) would make more sense. I'm sure no one at AWS would take a bug report seriously saying random FOSS thing doesn't work with their official client sdks...

[operator_nil]

I think it's too early to even say if Floci will become something that people use so time will tell, but at AWS, they already had some "informal" support for localstack[1] and it's always been a "commercial product" (so you can imagine how controversial it must be internally to support a third-party clone). I'm only saying that a FOSS version is somewhat less controversial for them to support and although I would love for AWS to have something of their own they clearly have other priorities.

[1] https://docs.aws.amazon.com/prescriptive-guidance/latest/pat...

[zach_vantio]

100% this. especially with agentic workflows actually mutating state now. local testing is the only safe way to see what happens when a model hallucinates a table drop without burning an actual staging database.