1. Docs
  2. Pulumi Cloud
  3. Deployments
  4. Time-to-Live Stacks

Time-to-Live Stacks

    Every Platform Team is familiar with the challenge of managing infrastructure that’s easy to spin up but often forgotten, leading to inflated costs and operational burden to manage. Time to Live (TTL) Stacks in Pulumi Cloud enable the automated management of stack lifecycles by specifying a predefined duration after which the stacks are automatically terminated. This feature is essential for managing ephemeral environments, such as development and testing setups, which do not require permanent infrastructure and can benefit from automatic decommissioning to avoid unnecessary costs and resource usage.

    Setting a Time-to-Live on a Stack

    Pulumi Cloud UI

    In order to set up Time-to-Live Stacks in the Pulumi Cloud console, follow these steps:

    1. Ensure Deployments Settings are configured on the stack see the docs
    2. Navigate to the Stack > Settings > Schedules
    3. Select “Time-to-Live”
    4. (Optional) Turn on “Delete After Destroy” if applicable
    5. Set the schedule using a cron expression
    6. Save the Schedule

    You will now see a schedule in the Schedules tab which highlights when the destroy will occur.


    For those who prefer to automate and script their infrastructure tasks, Time-to-Live schedules can be configured programmatically using simple HTTP requests.

    • Create a Time-to-Live schedule
    • Get a Time-to-Live schedule for a stack
    • Update or delete a Time-to-Live schedule
    • Pause or resume a Time-to-Live schedule
    • List all schedules in the organization (includes raw Pulumi operations and Drift schedules)

    Below is an example of setting up Time-To-Live on a stack programmatically:

      curl -H "Accept: application/vnd.pulumi+json" \
           -H "Content-Type: application/json" \
           -H "Authorization: token $PULUMI_ACCESS_TOKEN" \
           --request POST \
           --data '{"timestamp":"2024-12-31T23:59:59Z","deleteAfterDestroy":true}' \

    Refer to the Pulumi Deployments REST API documentation for more details on how to use the REST API to manage Time-to-Live Stacks.

    Pulumi Cloud Service provider

    The Pulumi Service Provider allows you to set up and manage Time-to-Live Stacks in source control.

    import * as pulumi from "@pulumi/pulumi";
    import * as pulumiservice from "@pulumi/pulumiservice";
    const organizationName = "my-org";
    const projectName = "my-project";
    const stackName = "temp-stack";
    const ttlSchedule = new pulumiservice.TtlSchedule("ttlSchedule", {
      organization: organizationName,
      project: projectName,
      stack: stackName,
      timestamp: "2024-01-01T00:00:00Z" // Specify the ISO date/time for destruction
    export const scheduleId = ttlSchedule.scheduleId;
    import pulumi
    import pulumi_pulumiservice as pulumiservice
    organization_name = "my-org"
    project_name = "my-project"
    stack_name = "temp-stack"
    # Create a TTL schedule for stack destruction
    ttl_schedule = pulumiservice.TtlSchedule("ttlSchedule",
        timestamp="2024-01-01T00:00:00Z") # Specify the ISO date/time for destruction
    pulumi.export('scheduleId', ttl_schedule.schedule_id)
    package main
    import (
    func main() {
        pulumi.Run(func(ctx *pulumi.Context) error {
            ttlSchedule, err := pulumiservice.NewTtlSchedule(ctx, "ttlSchedule", &pulumiservice.TtlScheduleArgs{
                Organization: pulumi.String("my-org"),
                Project: pulumi.String("my-project"),
                Stack: pulumi.String("temp-stack"),
                Timestamp: pulumi.String("2024-01-01T00:00:00Z"),  // Specify the ISO date/time for destruction
            if err != nil {
                return err
            ctx.Export("scheduleId", ttlSchedule.ScheduleId)
            return nil
    using Pulumi;
    using PulumiService = Pulumi.PulumiService;
    class Program
        static Task<int> Main() => Deployment.RunAsync(() => {
            var ttlSchedule = new PulumiService.TtlSchedule("ttlSchedule", new PulumiService.TtlScheduleArgs
                Organization = "my-org",
                Project = "my-project",
                Stack = "temp-stack",
                Timestamp = "2024-01-01T00:00:00Z",  // Specify the ISO date/time for destruction
            return new Dictionary<string, object?>
                { "scheduleID", ttlSchedule.ScheduleId }
    import com.pulumi.Context;
    import com.pulumi.Pulumi;
    import com.pulumi.pulumiservice.TtlSchedule;
    import com.pulumi.pulumiservice.TtlScheduleArgs;
    public class App {
        public static void main(String[] args) {
        private static void stack(Context ctx) {
            var ttlSchedule = new TtlSchedule("ttlSchedule", TtlScheduleArgs.builder()
                .timestamp("2024-01-01T00:00:00Z") // Specify the ISO date/time for destruction
            ctx.export("scheduleID", ttlSchedule.scheduleId());
    name: ttl-schedule-setup
    runtime: yaml
    description: Setup of TTL for automatic resource destruction with Pulumi
        type: pulumiservice:index:TtlSchedule
          organization: my-org
          project: my-project
          stack: temp-stack
          timestamp: "2024-01-01T00:00:00Z" # Specify the ISO date/time for destruction
      scheduleId: ${ttlSchedule.scheduleId}

    See the Pulumi Service Provider documentation for more details on how to manage Time-to-Live Stacks in source control.

      PulumiUP - September 18, 2024. Register Now.