← Chronicle
Hector Ventura//

Release Train: October 2026

Now It Really Runs

All over Floci, things that used to only look right now actually happen: Compute Engine instances that boot, Spark jobs that can fail, Azure policies that deny. What you can do with the October 31 release, and what it is preparing.

releaseannouncementopen-source

On October 6 I wrote that Compute Engine in Floci “doesn’t start real virtual machines”. Twenty-five days later, you can set one variable and every instance you create is a real running container.

That is the story of this release. All over Floci, things that used to only look right now actually happen. An EMR step used to finish on a timer and could never fail. An Azure policy could say “deny” and nothing was ever denied. In this release, those things run.

  • AWS: floci/floci 2.4.0
  • Azure: floci/floci-az 0.16.0
  • Google Cloud: floci/floci-gcp 0.12.0
  • Oracle Cloud: floci/floci-oci 0.6.0

What you can do now

Boot a Compute Engine instance on your laptop. Set FLOCI_GCP_SERVICES_COMPUTE_MOCK=false and instances.insert starts a container from the boot image. It runs cloud-init and your startup scripts, reaches the metadata server, and publishes the ports your firewall rules open. Give it a gce-container-declaration and it runs that container too. It’s still a container and not a virtual machine, but your bootstrap script now really executes (#472).

Run a Spark job and watch it fail. Set FLOCI_SERVICES_EMR_RUNNER_MODE=docker or FLOCI_SERVICES_EMRSERVERLESS_RUNNER_MODE=docker, and spark-submit runs in a container of the real EMR Serverless image, against Floci’s own S3 and Glue. A bad job now fails, and the failure handling you wrote finally gets tested. Step Functions can drive it all from a state machine. This is @pgermosen’s work (#6469, #6578).

Test your Azure deployment and your guardrails together. az deployment group create, Terraform’s azurerm_resource_group_template_deployment and compiled Bicep all work now, including nested templates and whatIf (#555, #556). @Tal-E made policies evaluate on every write (#451). Template resources go through the same path as any other request, so a template that breaks a deny policy gets the same 403 RequestDisallowedByPolicy you’d see on Azure.

Try AWS’s newest thing the same month it launched. AWS announced Lambda Web Functions on October 12. Three days later @exoego merged the control plane (#5706). Now aws lambda-web deploy works against Floci and your endpoint serves your code from a real Node.js container (#5760).

Connect to a real PostgreSQL behind managed databases. Each Aurora DSQL cluster, from @alessandrolattao, is PostgreSQL 16 behind DSQL’s endpoint, TLS and IAM tokens (#6102). OCI Database with PostgreSQL starts its own PostgreSQL container and only turns ACTIVE when it accepts connections (#74).

There’s plenty more: DynamoDB backups and point-in-time restores, Redshift work from @vuthehuyht, BigQuery copy jobs from @gafiatulin, Oracle Cloud Organizations. It’s all in the release notes above.

What this is preparing

Some of the most important work in this release you won’t notice, and that’s on purpose.

Real is opt-in, and that’s the design. Look at the variables above. The EMR default is still immediate. Compute Engine still defaults to the mock. Azure’s stricter answers sit behind FLOCI_AZ_PARITY, and it defaults to compat. Your test suite stays fast and keeps passing tomorrow, and you turn on the real thing where you need it. I expect more of Floci to work this way.

Azure got a real foundation. Every Azure service used to keep its resources in its own way. Now each one declares its resource types once (#485), and services are moving onto one shared store (#507). Template deployments, global names and policy can work across services because of it, and the next service gets all of that for free.

AWS’s rules come from AWS’s own model. @pgermosen moved IAM and STS request validation from hand-written checks to AWS’s published models (#6965, #6891). A bad request gets refused for the reason AWS would refuse it.

One way to talk to a console. The AWS and Azure emulators now describe themselves through the same manifest, Console Contract v2 (#6711). That’s what a single console across clouds needs.

Ready to stay running. @benwart-consensus, in their first contributions to Floci, split DynamoDB’s storage so a busy little table stops rewriting every big one beside it (#6303, #6310). It’s opt-in too, and it matters once Floci is something you leave running, not just start for a test.

None of this is finished. Aurora DSQL and EMR are both still open, and if you hit something that doesn’t behave like the real cloud, that’s the issue I want to read.

Thank you

78 people merged 1,187 pull requests in the sixteen days behind this release. For 32 of them, it was their first time contributing to any of the emulators. Welcome:

@4Raisan, @andrehoong-px, @andrei-fabricdata, @baseballyama, @benwart-consensus, @bercedev, @bfs2021, @brito219, @dkatavic, @gafiatulin, @gagalago, @galsuchetzky-act, @isak-lindbeck, @JimmyLiuJia, @joelklint, @kenny-ish, @Keralin, @kozhinhikkodan-dev, @liRONCO11, @MosesWayCo, @mrjusepelo, @renalddubus, @Ridzzz0Alam, @ScottishTapWater, @Sekator778, @seniorescobar, @sujashaj, @T-Webb1, @tkislan, @vinirib, @wleeaf, @xHUNx.

Sponsors keep Floci free. Sponsorship buys gratitude and nothing else, so here is the gratitude:

Thanks as well to everyone sponsoring privately.

Floci stays free, MIT-licensed, no gates, no telemetry.

The next release is on November 15.

Join the Flock: GitHub · r/floci · Slack · floci.io

Any Cloud. Locally. Let’s keep Emulating.