Configuration

Principles of stack 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.

Have questions not answered here? Contact Support to get more help.

Last modified on August 24, 2026