The taken approach doesn't matter much. If needed, it's easy to refactor to the other in the future.

Initially this approach is okay, however in the future we should switch from log parsing to direct interaction with cloudwatch metrics, by using aws_sdk_cloudwatch crate

Nice work on this! Looks neat, good job on handling async tasks and graceful shutdown.

LGTM, nice

Flip the flag only for native

Copy feedback

Ideally, instead of this mechanism with polling from Tunnelbroker, we should've used a stream, but this is a lot more work (things like setting up Lambda).

Registration utils could be refactored and written in a better way but it's not worth focusing on this now

Should we have a note on both sides (Rust, JS) to keep them in sync?

Thanks for explaining!

Nice, I've left some suggestions but they're rather follow-ups for better API design, unless you find something helpful for now, you can ignore them. We can always refactor it later when the API and our needs are better determined

Nice!