Before you start
You need an Ecocloud account with Cloud Shell available. Use a trusted browser and sign in to the account that owns the resources you want to inspect.
The demonstration below needs no account. It uses sample data and does not open a real Cloud Shell session.
See Cloud Shell in action.
Watch Cloud Shell open beside the dashboard, type a command and return sample output. Pause the presentation whenever you want a closer look.
Everything in its place.
Your application, its resources and the tools to operate it.
| Resource | Runtime | Network | State |
|---|---|---|---|
| web-01 | Virtual machine | application-net | Running |
| api-worker | Container | application-net | Running |
| order-webhook | Function | application-net | Ready |
Animated example: Cloud Shell opens beside the dashboard, types a help command and lists sample services. No real session is started.
01 / Open
Start from your console.
Open Cloud Shell after signing in. Check the availability message and session limits, then choose Start Cloud Shell. Wait for the workspace to become ready before entering a command.
Starting a real session provisions an isolated runtime with a temporary home directory. The preview above does not provision this runtime.
02 / Inspect
Discover a command. Read its result.
Start with help for an overview, or ask for help with a specific operation:
ecocloud --help
ecocloud help services listList the services available to your account:
ecocloud services listFor structured output, request JSON:
ecocloud services list --output jsonThe table includes resource identifiers, names, types and reported states. An empty list can simply mean this account has no matching services. A running state alone does not confirm that an application is healthy.
Check your result
Confirm that the expected service appears and that you are using the intended account. Compare its reported state with the resource view in the console. You have completed a read operation; listing services does not change them.
03 / Finish
Save the useful part. End the session.
Check the idle and absolute session deadlines shown in the workspace. Save files or output you need outside its temporary home directory before ending the session.
Use a virtual machine, container or function to host an application that needs to keep running.
Keep workspace and guest access separate.
Your shell session follows account policy. It does not automatically grant root access to virtual machines. Guest administration requires the correct credentials and a permitted connection path; write operations also retain their own authorization requirements.
If something does not work
Cloud Shell is unavailable
Read the availability or policy message in the console. Confirm you are using the intended account; the example on this page does not indicate live workspace availability.
A command is not recognised
Run ecocloud --help and check the command spelling and supported options. The CLI command catalog is the source of truth for your environment.
The service list is empty or access is denied
Confirm the current account and its access to the expected resource. Do not assume that access to one resource grants access to another.
My session ended
Check the displayed deadline or session state. Start another session if available, and restore any needed work from the copy you saved outside the temporary workspace.