PLATFORMS Signal 172
FlowG team uses floci to emulate AWS, GCP, and Azure log services for CI/CD testing
↗
Illustration only Photo by imgix on Unsplash
The FlowG project adopted floci to locally emulate AWS CloudWatch, Google Cloud Logging, and Azure Monitor, avoiding per-provider cloud accounts and costs in CI/CD pipelines.
floci runs via a single Docker command and accepts any string as credentials, making it cheap to test cloud log-forwarding integrations in CI. However, the lack of real authentication means teams still need at least one manual test against each provider to verify production credential handling.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
floci emulates AWS CloudWatch, Google Cloud Logging, and Azure Monitor locally via Docker, letting teams test log integrations without cloud accounts or per-run costs.
AWS integration was straightforward; GCP required floci-gcp after other emulators failed; Azure needed HTTPS, a custom auth token implementation, and two client libraries.
floci skips authentication entirely, so it validates integration logic but not real credential handling against actual provider infrastructure.
THE CLUSTER