When a FinOps or CloudOps process needs to take action, the last mile often happens outside your tooling: someone opens a terminal, runs a one-off CLI command, pastes output into a ticket, and hopes the next person follows the same steps. That breaks auditability and makes repeatable governance hard, especially when you’re promoting artifacts between environments or responding to an incident under time pressure.

CloudFlow now includes a CLI node, so you can run AWS or GCP commands as a first-class step inside a flow, alongside the rest of your automation. This lets you encode terminal-only procedures as an automated, repeatable workflow with a run history, rather than relying on tribal knowledge and manual execution.

For example, a storage expansion workflow can attach an existing EBS volume to an EC2 instance using the same CLI command you already know, but executed as part of the flow. Under the hood, the CLI action maps to the same API sequence you’d expect (validation, state checks, then the attach call), which makes the operation predictable and easier to reason about when troubleshooting.

Similarly, release or data movement workflows that “S3 sync” become explicit, repeatable building blocks. In S3, “move” is actually a copy-and-delete operation, and encoding that once in a flow reduces accidental deviations between operators and environments.