FlowG adds AWS, GCP and Azure log forwarders ahead of 1.0 release, using floci for local testing

The FlowG team is preparing its 1.0 release and identified a gap: no native integrations with the logging services of AWS, Google Cloud, and Azure, despite already supporting eight general-purpose forwarders. To build and test the AWS CloudWatch integration without incurring cloud costs or needing live accounts, they used floci, a local emulator launched via a single Docker command, which let them configure the AWS SDK to hit a local endpoint and verify log forwarding using standard CLI tools.