Configuration

Connecting to an existing stack

When deploying multiple stacks within the same environment, the Webscale Control Plane acts as a central dependency resolver. Instead of referencing cloud-provider resources directly, a stack may reference outputs from another stack

For example, you may wish to deploy an add-on stack into an existing network or require the database endpoint of an RDS database. To refer to these values, you can provide references to the outputs from a different stack.

Examples

  "data_subnets": "/v2/stacks/{stack-id}/outputs/data_subnets"
  "public_subnets": "/v2/stacks/<{stack-id}/outputs/public_subnets"
  "db_endpoint": "/v2/stacks/<{stack-id}/outputs/db_endpoint"
  "db_password_secret_name": "/v2/stacks/<{stack-id}/outputs/db_password_secret_name"

Note: A stack that is referenced by another stack cannot be deleted until the dependency is removed.

Deletion protection

A stack cannot be deleted while any of its resources has deletion protection turned on. The delete request returns a 409 Conflict error and no resources are removed.

Core servers

Stacks with a core server turn on deletion protection by default to stop the core server from being removed by accident. The server.deletion_protection variable controls it.

To delete the stack, update it to set server.deletion_protection to false, wait for the stack to finish synchronizing, and then delete it.

Example

{
  "variables": {
    "region": "us-east-1",
    "size": "medium",
    "server": {
      "deletion_protection": false
    },
    "stacker_variables": {
      ...
    }
  }
}

RDS

If deletion protection is turned on for an RDS database, turn it off before you delete the stack.

Last modified on October 27, 2026