Projects and environments
How CloudBooster organises your infrastructure: projects, environments, and the resources that live inside them.
Projects and environments
CloudBooster organises your infrastructure in two layers: projects and environments.
Every ChangeSet, security finding, deployment run, and cost data point belongs to a specific environment. Approval rules, access control, and policies are configured at the project level and inherited downward.
Projects
A project is a logical grouping of environments that belong together — typically one product, one microservice cluster, or one team's infrastructure.
Projects give you a place to:
- Define approval rules — who must sign off before a ChangeSet can be applied (see Approval rules).
- Set access control — which organisation members can see or modify the project.
- Browse history — a timeline of every change ever applied across all environments.
- Configure project-level settings such as the default cloud profile.
Environments
An environment represents one deployment target inside a project. Every environment maps to a connected AWS account (or a region within one).
Environments have a type:
| Type | Typical use |
|---|---|
development | Local iteration and feature work |
staging | Pre-production integration and QA |
production | Live infrastructure serving real traffic |
The type is informational — it affects labels and some workflow defaults but does not technically restrict what you can deploy.
What lives in an environment
Inside each environment you will find:
- Infrastructure map — a visual topology of all deployed components.
- ChangeSets — the queue of proposed, approved, and applied changes.
- Findings — security and compliance issues detected by continuous scanning.
- Deployment runs — an execution log of every apply operation.
- Cost data — per-environment spend fed into the Cost Explorer.
Cloud profile
Each environment is linked to a cloud profile — a CloudBooster name for a connected AWS account. The same AWS account can serve multiple environments (common in development); distinct production accounts each have their own profile.
To connect a new AWS account, follow the Connect an AWS account guide.
Creating a project
Projects are created from the portal. Navigate to Projects in the top navigation, choose New project, give it a name, and optionally assign a default cloud profile. You can add environments after the project is created.
Environment access
Environment-level access is inherited from project membership by default. Owners can restrict individual environments to a subset of project members — useful when production access should be limited to a smaller group.