Skip to content
Reoclo Docs

Cloud Credentials

Cloud credentials let you connect your cloud provider accounts to Reoclo. Once connected, you can discover existing cloud instances, link them to Reoclo servers, and perform power operations (reboot, shutdown) directly from the dashboard.

Supported Providers

Section titled “Supported Providers”
ProviderOperations
HetznerDiscover, link, reboot, shutdown, power on
DigitalOceanDiscover, link, reboot, shutdown, power on
AWSDiscover, link, reboot, shutdown, power on
VultrDiscover, link, reboot, shutdown, power on
LinodeDiscover, link, reboot, shutdown, power on

Adding Credentials

Section titled “Adding Credentials”
  1. Navigate to Cloud Providers in the sidebar
  2. Click Add Credential
  3. Select your cloud provider
  4. Enter a label and your API token or access key
  5. Click Verify to confirm the credential works
  6. Click Save

Credentials are encrypted at rest using AES-256-GCM envelope encryption.

Provider-Specific Tokens

Section titled “Provider-Specific Tokens”

Hetzner: Generate an API token in the Hetzner Cloud Console under Security > API Tokens. Use Read & Write permissions.

DigitalOcean: Create a Personal Access Token in the API settings with read and write scopes.

AWS: Use an IAM Access Key ID and Secret Access Key. The IAM user needs EC2 permissions for instance discovery and power operations.

Vultr: Generate an API key in the Vultr API settings.

Linode: Create a Personal Access Token in the Linode Cloud Manager with read/write access to Linodes.

Discovering Instances

Section titled “Discovering Instances”

After adding credentials, click Discover Instances to scan your cloud account for existing servers. Reoclo will:

  1. List all instances from your cloud provider
  2. Match them to existing Reoclo servers by IP address or provider instance ID
  3. Show which instances are already linked and which are new

For each discovered instance, you can see:

  • Instance name and status
  • IP addresses
  • Region and specs (CPU, RAM, disk)
  • Monthly cost
  • Whether it’s already linked to a Reoclo server

Linking Instances

Section titled “Linking Instances”

To link a discovered cloud instance to an existing Reoclo server:

  1. Click Link next to the instance
  2. Select the Reoclo server to link it to
  3. Confirm

Once linked, Reoclo can use the cloud provider API for power operations on that server, which is faster and more reliable than sending commands through the runner agent.

Power Operations

Section titled “Power Operations”

With linked cloud credentials, these operations use the cloud provider API:

  • Reboot: Triggers a graceful reboot via the provider API
  • Shutdown: Powers off the server via the provider API
  • Power On: Starts a powered-off server

Reoclo uses smart routing: it tries the cloud API first, then falls back to the runner agent if the cloud API fails.

Verifying Credentials

Section titled “Verifying Credentials”

Use the Verify button to test that your credentials are still valid. Reoclo will attempt to authenticate with the provider and update the credential status:

  • Active: Credential is valid and working
  • Invalid: Authentication failed (check your token)

Revoking Credentials

Section titled “Revoking Credentials”

Revoking a credential marks it as inactive. Linked servers will fall back to runner-only operations for reboots and power management.

Next Steps

Section titled “Next Steps”