> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackshift.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# BYOCloud cloud resources

> Manage provider-backed node resources such as volumes, snapshots, placement metadata, stable public IPs, refresh, retry, reboot, and delete actions from the node detail surface.

<Tip>
  **Live.** This area is documented as current, user-reliable behavior.
</Tip>

## 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

<Steps>
  <Step>
    Open the Cloud resources section on a BYOCloud node.
  </Step>

  <Step>
    Refresh provider state and inspect placement, addressing, and tracked cloud resources for that node.
  </Step>

  <Step>
    Create, inspect, detach, or safely delete provider-backed volumes where supported.
  </Step>

  <Step>
    Create and review volume snapshots where the provider supports snapshots.
  </Step>

  <Step>
    Allocate or release a stable public IP where supported, and use retry, reboot, or delete node actions when needed.
  </Step>
</Steps>

## 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

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

## Common failures

<Warning>
  * Volume is still attached during delete
  * Snapshot is still creating
  * Static IP quota is exhausted
  * Provider placement or address metadata drifted
</Warning>

## Related guides

<CardGroup cols={2}>
  <Card title="BYOCloud overview" href="/nodes/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.
  </Card>

  <Card title="Connect a BYOCloud node" href="/nodes/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.
  </Card>

  <Card title="Nodes view" href="/operations/nodes-view">
    Use the node-focused operations surface when you need to think about capacity, health, and runtime readiness across hosts.
  </Card>
</CardGroup>