Time to Live (TTL)
Define how long an environment should be up and running
Overview
Environment TTL (Time to Live) lets you schedule the automatic uninstallation of an environment. Instead of relying on someone to manually tear down infrastructure, you define a recurring daily or weekly schedule and Bluebricks uninstalls the environment at the specified time.
How environment TTL works
TTL supports intentional environment management. You can shut down dev, staging, or sandbox environments outside business hours to control cloud spend, align teardown with maintenance windows, or ensure environments follow internal operational standards. It also helps prevent environments from running longer than intended, reducing drift and maintaining cleaner collections.
Each environment includes a dedicated Environment TTL tab on its detail page. From this tab, you can create, edit, enable, or disable a TTL schedule.

When a TTL schedule triggers, Bluebricks starts an uninstall run for the environment, the same operation as a manual uninstall. The run follows the standard environment lifecycle: it evaluates the blueprint, builds a destroy plan across all packages, and tears down resources in the correct dependency order. The run appears in the environment's history with full logs and status tracking.
The uninstall follows the same policies and approval flows configured on the target collection. If an approval policy is in place, the scheduled uninstall respects it.
A TTL schedule does not delete the environment itself. It uninstalls the deployed resources. The environment record, history, and configuration remain intact. You can re-run the environment at any time.
How to set up a TTL schedule
Turn on TTL
Go to the Environment page and click Review on the environment you want to configure
Click the Environment TTL tab
Turn on the toggle, which will open the scheduler
Create a schedule
Choose a recurrence type: Daily or Weekly
Set the time in hours and minutes using 24-hour UTC time
For weekly schedules, select which days the uninstall should run
Click save
TTL schedules run under a dedicated system identity. The uninstall run is attributed to the scheduler, not to a specific user.
Edit or disable TTL
You can edit or disable Environment TTL at any time to change the recurrence, adjust the time, or disable the schedule. Disabling preserves your configuration so you can re-enable it later without reconfiguring.
Last updated
Was this helpful?

