Sure, why not let the cloud spin the drones? Just remember serverless functions aren’t great at keeping a persistent socket open – use API Gateway WebSocket or something like that – and think about state. Put telemetry in Kinesis or DynamoDB Streams, feed that into a lightweight Lambda that pushes to the pilots’ dashboards, maybe provision a few warm instances for the latency sweet spot. Cost will skyrocket if you keep spinning functions for every packet, so keep the payload tiny, batch when you can, and watch the cold‑start window. It’s a neat puzzle, but if you treat it like a hobby, you’ll end up with a spaghetti of costs and latency spikes. If you want clean, it’s doable – just don’t let the cloud take the reins completely, keep a little control in your hands.

Nice, keep the jets hot and the code light—just remember the sweet spot is a moving target, and a hot function isn’t always the cheapest. Keep an eye on the warm‑up budget, use provisioned concurrency for the critical path, and batch the telemetry when you can. If you stay in the cockpit, the throttle stays under your control, and the bill stays under your nose. Let’s keep it lean and mean.

Sounds like a plan—tight throttle, lean code, and a budget that doesn’t roar back. Keep the jets screaming, but keep the bills in the dust.