Projects

Projects are isolated containers for your cloud resources. Each project provides a separate scope for VMs, storage, networking, and other resources, with its own access controls and quota tracking.

What projects provide

Projects give you:

• Resource isolation - Resources in different projects are completely separate
• Access control - Each project has its own role bindings controlling who can access it
• Quota tracking - Some resource usage is tracked per project

Project structure

Projects have a flat structure. You can't nest projects within each other, but you can create as many projects as you need within your organization.

Common patterns for organizing projects include:

• By environment - dev, staging, production
• By team - frontend, backend, data-platform
• By application - web-app, api-service, batch-jobs

Organization
├── dev
├── staging
├── production
├── data-platform
└── shared-services

Working with projects

Creating projects

Create a project using the evroc CLI:

evroc iam project create my-project --name "My Project"

For step-by-step instructions, see Create a project.

Listing projects

List all projects you have access to:

evroc iam project list

Switching projects

Set your current working project for CLI operations:

evroc config set-project my-project

All subsequent commands operate on this project until you switch to another.

Access control

Access to a project is controlled through role bindings. A principal needs a project role binding to access resources in that project.

Project-level role bindings grant access only to that specific project. Organization-level roles govern organization operations and don't grant access to project resources.

To grant project access, create or update a role binding. See Manage role bindings for instructions.