Scaling Compute Resources
Update CPU, memory, and VM sizes for deployed workloads by changing blueprint inputs and re-running environments
Overview
Scaling compute resources (CPU, memory, VM size) is one of the most common Day 2 operations. In Bluebricks, you change the relevant blueprint input values and start a new run of the environment. The underlying IaC engine handles the cloud provider API calls to resize or reconfigure your resources.
Prerequisites
An existing environment with a completed run
The blueprint exposes inputs for the compute properties you want to change (e.g.,
vm_size,instance_type,cpu_cores,memory_gb)Access to the collection that the environment belongs to
How to scale compute resources
Update the compute-related input in your environment manifest file and push the change. If you use GitOps environments, Bluebricks triggers a plan automatically. For PR-based workflows, the plan posts to your pull request for review before merging.
# environment manifest (e.g., web-app-prod.yaml)
inputs:
vm_size: "Standard_D4s_v3"See Managing Configuration on Git for the full manifest format.
Open the Environments page and go to the environment you want to update
In the three-dot menu click Deploy
Update the compute-related input values (e.g., change
vm_sizefromStandard_D2s_v3toStandard_D4s_v3)Review the plan to confirm the change is in-place
Click Deploy
Pass the updated input values using --props or --props-file:
bricks install web-app \
--collection=production \
--env-slug=web-app-prod \
--props '{"vm_size": "Standard_D4s_v3"}'Or use a properties file:
bricks install web-app \
--collection=production \
--env-slug=web-app-prod \
--props-file=./updated-props.jsonAdd --plan-only first to preview the change without applying it:
bricks install web-app \
--collection=production \
--env-slug=web-app-prod \
--props '{"vm_size": "Standard_D4s_v3"}' \
--plan-onlyCommon compute changes
Increase CPU or memory
Most cloud providers bundle CPU and memory into instance or VM sizes. To scale up, change the VM size input to a larger tier:
Azure
vm_size
Standard_D2s_v3 to Standard_D4s_v3
AWS
instance_type
t3.medium to t3.xlarge
GCP
machine_type
e2-medium to e2-standard-4
Change VM series or family
Switching between VM families (e.g., from general-purpose to compute-optimized) follows the same workflow. Update the VM size input to the new family:
Cloud provider behavior
How a compute change is applied depends on the cloud provider. Most resize operations require a brief stop/start cycle but preserve attached storage and network configuration.
What to check after scaling
Run status: confirm the run completed successfully in the environment's run history
Resource state: verify the new compute configuration in your cloud provider console
Application health: check that your workloads are running correctly after the resize
Drift detection: if drift detection is enabled, the next check should show no drift
Last updated

