Use AI Cloud
This section groups the operational guides for people using AI Cloud.
Guides
| Guide | Use it when |
|---|---|
| Platform Capabilities | You need to know what AI Cloud already exposes through UI, CLI, SDK, and API. |
| AI Cloud User Guide | You need a complete task-based user guide from first sign-in through launch, connect, release, CLI, SDK, and troubleshooting. |
| Quickstart | You need the first end-to-end launch walkthrough. |
| Resource Hierarchy And Roles | You need to understand ownership, role, project, and billing context. |
| User Onboarding | You are signing in and preparing your account for the first time. |
| Launch Compute | You need direct GPU or CPU capacity and a concrete launch/connect/release path. |
| Launch And Operate | You need to launch compute, apps, notebooks, schedulers, or endpoints. |
| Tenant Administration | You manage users, projects, service accounts, quota, and spend. |
| Troubleshooting Playbook | A flow is blocked or a workload needs recovery. |
Normal Work Pattern
- Confirm tenant and project.
- Confirm account security and access keys.
- Choose the runtime family.
- Review cost, quota, storage, and access prerequisites.
- Launch.
- Connect through the supported runtime action.
- Monitor state, usage, and spend.
- Release the runtime when finished.
Product Surfaces
| Surface | Primary use |
|---|---|
| Workloads | Active runtimes, status, connect actions, release actions. |
| Compute | Raw GPU node or slice capacity launch. |
| Apps | Packaged runtime catalog and app launch. |
| Storage | Buckets, data substrate, and storage ownership posture. |
| Access | Projects, members, identities, service accounts, and credentials. |
| Account | Profile, billing, MFA, sessions, SSH keys, and API keys. |
Minimum Self-Service Path
For a new user, the intended self-service path is:
- AI Cloud User Guide
- Platform Capabilities
- Quickstart
- Resource Hierarchy And Roles
- Account Security
- Launch Compute or Launch And Operate
- Billing And Storage
- Troubleshooting Playbook if a blocked state appears
Good Operating Habits
- Keep tenant and project context visible before launching work.
- Release unused capacity promptly.
- Prefer product-visible correlation IDs over screenshots of secrets.
- Use service accounts for automation rather than shared user credentials.
- Review stale access, stale sessions, and long-running workloads regularly.