Connect Cloud Accounts

Connect cloud accounts to environments (collections) in Bluebricks. Each environment corresponds to a collection in the platform, and connecting a cloud account tells Bluebricks where that collection's deployments will run.

Prerequisites

• Bluebricks CLI installed

• Authenticated with Bluebricks (bricks login)

• Existing environment (collection)

• Cloud account credentials

What Are Cloud Accounts?

Cloud accounts in Bluebricks:

• Provide cloud credentials for deployments

• Connect to specific cloud providers (AWS, GCP, Azure)

• Enable resource creation in the target collection

• Manage cloud permissions and access

Cloud Account Connection

AWS Connection

# Connect AWS account to environment
bricks setup aws --collection production

# Verify AWS connection
bricks collection ls

Note: Currently only AWS is supported via CLI with bricks setup. For GCP, Azure, and other providers, use the Bluebricks web interface.

Connection Process

1. Check Environment

# List environments
bricks collection ls

# Check environment status
bricks collection ls --all

2. Connect Cloud Account

# Connect cloud account
bricks setup aws --collection my-environment

3. Verify Connection

# Check environment status
bricks collection ls

# Verify cloud account appears

Connection Examples

Development Environment

# Connect AWS to development
bricks setup aws --collection development

# Verify connection
bricks collection ls

Production Environment

# Connect AWS to production
bricks setup aws --collection production

# Verify connection
bricks collection ls

Note: Multi-cloud setup requires using the Bluebricks web interface for providers other than AWS.

Connection Status

Connected Environment

GUID                                NAME           CLOUD PROVIDER   CLOUD ACCOUNT   SLUG              STATUS
----------------------------------- -------------- ---------------- --------------- ----------------- -------------------------
env-uuid-123                        production    AWS              aws-prod        production        DEFAULT, web-app (running)

Unconnected Environment

GUID                                NAME           CLOUD PROVIDER   CLOUD ACCOUNT   SLUG              STATUS
----------------------------------- -------------- ---------------- --------------- ----------------- -------------------------
env-uuid-456                        development   -                -               development       -

Connection Management

Check Connection Status

# List environments with cloud account info
bricks collection ls

# Check all environments
bricks collection ls --all

Reconnect Cloud Account

# Reconnect cloud account
bricks setup aws --collection my-environment

Connection Best Practices

Collection Organization

• Connect appropriate cloud accounts to each collection

• Use separate cloud accounts for different collections

• Keep production and development separate

Security

• Use least-privilege cloud credentials

• Regularly rotate cloud credentials

• Monitor cloud account access

Monitoring

• Check connection status regularly

• Verify cloud account connectivity

• Monitor deployment success

See also

• Connect your Cloud -- full cloud connection guide with provider-specific instructions

• Collections -- collection concepts and permissions

• How to Connect AWS -- AWS-specific connection steps