Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
Goal

Explain the current BYOCloud cloud resource and node operation surface available from the Nodes page.

​
Prerequisites

  • A provisioned BYOCloud node
  • A provider that supports the resource type you want to use

​
Workflow

1
Open the Cloud resources section on a BYOCloud node.
2
Refresh provider state and inspect placement, addressing, and tracked cloud resources for that node.
3
Create, inspect, detach, or safely delete provider-backed volumes where supported.
4
Create and review volume snapshots where the provider supports snapshots.
5
Allocate or release a stable public IP where supported, and use retry, reboot, or delete node actions when needed.

​
Current provider support

  • AWS: EBS volumes, EBS volume snapshots, VPC/subnet/AZ metadata, Elastic IPs
  • DigitalOcean: block storage volumes, volume snapshots, region/network metadata, Reserved IPs
  • Hetzner: cloud volumes, location metadata, Floating IPs; attached-volume snapshots are intentionally unsupported

​
Available operations

  • Refresh node cloud resources and provider metadata
  • Create and attach volumes with StackShift-managed mount path and filesystem defaults
  • Detach and safely delete managed volumes
  • Create and delete volume snapshots where the provider supports snapshots
  • Allocate and release stable public IPs where the provider supports them
  • Retry failed provisioning, reboot a BYOCloud node, or request node deletion from the same surface

​
Operational model

  • Cloud resources are tracked as part of the node and surfaced through node detail, operation state, and reconciliation data.
  • Node and resource actions run through StackShift operations instead of direct provider-console workflows.
  • Placement, addressing, and resource metadata are shown to improve visibility, support, and day-two operations.
  • Provider-specific capability differences are reflected directly in the available actions for that node.

​
Expected result

Operators can provision and operate BYOCloud nodes and their supported provider-backed resources directly from StackShift.

​
Common failures

  • Volume is still attached during delete
  • Snapshot is still creating
  • Static IP quota is exhausted
  • Provider placement or address metadata drifted

BYOCloud overview

Connect customer-owned cloud accounts to StackShift, provision cloud-backed nodes, and operate them through the same node workflows used elsewhere in the product.

Connect a BYOCloud node

Save provider credentials, choose a tested region and StackShift tier, and wait for the provisioned cloud node to become healthy and schedulable.

Nodes view

Use the node-focused operations surface when you need to think about capacity, health, and runtime readiness across hosts.