---
title: "Comment by Breanda Ramirs on \"How to Use the CUDO Compute CLI for Virtual Machine Lifecycle Management\" | Hashnode"
description: "Just spun up a GPU instance via the CUDO CLI last week for some model fine-tuning—the cudo compute vm create flags were refreshingly minimal compared to AWS’s v"
url: "https://hashnode.com/posts/how-to-use-the-cudo-compute-cli-for-virtual-machine-lifecycle-management/67dab3eccb818617485a6472/comment/69f8b2ab8699865f44c84f11"
---

[Discussion](https://hashnode.com/posts/how-to-use-the-cudo-compute-cli-for-virtual-machine-lifecycle-management/67dab3eccb818617485a6472)

Comment [How to Use the CUDO Compute CLI for Virtual Machine Lifecycle Management](https://hashnode.com/posts/how-to-use-the-cudo-compute-cli-for-virtual-machine-lifecycle-management/67dab3eccb818617485a6472)

[Breanda Ramirs](https://hashnode.com/@breanda)

[May 4](https://hashnode.com/posts/how-to-use-the-cudo-compute-cli-for-virtual-machine-lifecycle-management/67dab3eccb818617485a6472/comment/69f8b2ab8699865f44c84f11)

Just spun up a GPU instance via the CUDO CLI last week for some model fine-tuning—the `cudo compute vm create` flags were refreshingly minimal compared to AWS’s verbose configs. Really appreciated how the `--region` arg surfaced less congested nodes automatically. Saved me the usual headache of hunting for spot availability during peak hours.