All users
Cloud Console Overview
Understand how the cloud console maps to projects, quotas, and infrastructure resources.
8 min read · Updated 2026-03-19
Prerequisites
- • Active cloud account
- • At least one project with quota
- • SSH public key generated locally
How the console is organized
The web console uses project-scoped resources, service menus for compute/network/storage, and role-based access controls.
Always confirm the active project before creating resources. Quotas and visibility are project-specific.
- Open the project selector and verify the target project.
- Review project quotas for vCPUs, RAM, volume storage, and floating IPs.
- Check the Overview dashboard for current usage and pending alerts.
Recommended first-day baseline
Before deploying workloads, establish baseline security and networking resources. This prevents repeated manual setup and accidental exposure.
- Create at least one key pair for SSH access.
- Create a security group with inbound SSH (22), HTTP (80), and HTTPS (443) only when needed.
- Create one private network, subnet, and router with external gateway.
- Set budget alerts and notification contacts.
Operational hygiene
Treat cloud resources as managed inventory. Consistent naming and tagging reduces troubleshooting time and billing ambiguity.
Operator tips
- • Use resource name patterns like env-app-role-index (prod-web-frontend-01).
- • Enable backup policies on any stateful resource before production cutover.
- • Rotate API tokens and SSH keys on a schedule.