docs(aws): add Quickstart checklist for launching clusters

[joshkodi]

What

Adds a Quickstart checklist at the top of the "Launching Ray Clusters on AWS" guide.

Why

Many new users want a short, actionable set of steps. This 4-step checklist (credentials, ray up, dashboard, and ray status) gives them a clear quickstart path.

How

• Edited doc/source/cluster/vms/user-guides/launching-clusters/aws.md
• Added a MyST note block with clean Markdown fencing and syntax-highlighted code.

Verification

• Ran make html locally and confirmed note block renders correctly.

[gemini-code-assist]

Code Review

This pull request adds a helpful Quickstart checklist to the AWS cluster launch guide. The intention is great for new users. I've provided a couple of suggestions to improve the clarity and consistency of the documentation. One suggestion is to make the quickstart self-contained by adding the command to download the example configuration file and to use a consistent filename throughout the document. The other is a minor formatting fix to ensure consistency in the Markdown syntax.

[gemini-code-assist]

The quickstart guide is a great addition for new users! However, there are a couple of points that could be improved for clarity and consistency:

1. The command ray up cluster.yaml assumes the user has a file named cluster.yaml. A new user following the quickstart won't have this file. It would be helpful to include the step to download the example configuration file.
2. The rest of this document refers to example-full.yaml. Using cluster.yaml in the quickstart is inconsistent.

I suggest using example-full.yaml consistently and adding the wget command to download it.

Suggested change

	**2) Bring up a cluster** using the example configuration:
	```bash
	ray up cluster.yaml
	```
	See the Cluster Configuration section for details.
	**3) Access the Ray Dashboard** at `http://<head-node-ip>:8265`.
	Ensure inbound TCP **8265** is allowed in your AWS Security Group.
	**4) Check cluster status:**
	```bash
	ray status
	```
	Optional: enable autoscaling by adjusting node settings in `cluster.yaml`.
	**2) Bring up a cluster** using the example configuration:
	```bash
	wget https://raw.githubusercontent.com/ray-project/ray/master/python/ray/autoscaler/aws/example-full.yaml
	ray up example-full.yaml

See the Cluster Configuration section for details.

3) Access the Ray Dashboard at http://<head-node-ip>:8265.
Ensure inbound TCP 8265 is allowed in your AWS Security Group.

4) Check cluster status:

ray status

Optional: enable autoscaling by adjusting node settings in example-full.yaml.

[joshkodi]

Thanks for catching these two things.

Added a new step to download the example cluster configuration file via curl.

Updated filename from cluster.yaml → example-full.yaml for consistency with the rest of the doc.

Rebuilt locally (make html) — renders cleanly.

[joshkodi]

Thanks everyone for the quick review — glad to contribute to Ray docs!

[gemini-code-assist]

While technically valid in MyST-Parser (closing fence must be at least as long as the opening one), using a different number of backticks for opening and closing a fenced block is inconsistent and can be confusing for future editors. The eval-rst block starting on line 180 opens with three backticks (```), so it would be more consistent to close it with three backticks as well.

Suggested change

````

[joshkodi]

Good catch, I have fixed the backticks to make it consistent

[joshkodi]

🙏 Thanks everyone for the thoughtful and speedy reviews!

I’ve incorporated all the feedback — added the step to download example-full.yaml, aligned the filename throughout, and fixed the fenced-block consistency.

Confirmed the build and render locally — everything looks good on my side.

Really appreciate the clear guidance and support on my first contribution to Ray docs! ⚡️

[jjyao]

It should be ## since it's under # Launching Ray Clusters on AWS

[joshkodi]

Updated, thanks Jiajun!