Creating Collections

Create collections from the Bluebricks app or CLI to organize infrastructure by team, project, or lifecycle stage

Overview

Collections organize infrastructure into clear units that match how teams actually work. You can create separate collections for projects, teams, or lifecycle stages such as development, staging, and production. Each collection provides the foundation for environments by holding shared settings and rules.

Example of creating a collection with AWS

How to create a collection via the Bluebricks app

1. Go to the Collections page

2. Click Create Collection

3. Enter a name for the collection

4. Select the cloud provider(s) to connect

   1. Haven't connected your cloud accounts yet? Learn how to connect your cloud

5. Configure any required settings, permissions, and secrets

6. Click Create to finalize the setup

How to create a collection via the CLI

You can create a new collection using the Bricks CLI (refer to Bricks CLI Installation Guide if you haven't installed it yet):

bricks collection create --name "Self-Hosted Orchestrator"

A successful creation displays a confirmation message with the new collection ID:

✓ `Self-Hosted Orchestrator` collection created successfully with ID: 42c9d5cf-cf9c-4783-ac1d-4d34140b9299

To set the new collection as the default target for commands that don't specify --collection:

bricks collection create --name "development" --default

Naming conventions

• Use clear, descriptive names: production, staging, development

• Include team or project context when needed: team-alpha-production

• Follow a consistent pattern across your organization: {project}-{stage}

After creating a collection, connect a cloud account before deploying. See Connect your Cloud. To manage existing collections (list, enable, disable, delete), see Managing Collections.