Cloud Auth

A Cloud Auth is a secure connection between your Daestro account and your account with a cloud provider like Amazon Web Services (AWS) or DigitalOcean. Think of it as giving Daestro a special, secure key that allows it to manage servers on your behalf.

This connection is necessary because Daestro runs your tasks (jobs) directly within your own cloud account. This gives you full control and means you pay your cloud provider directly for any servers you use. Daestro only charges its own separate fee for providing the management platform.

How Daestro Keeps Your Account Safe

To connect your account, you’ll provide an API Key from your cloud provider. Daestro treats this key with the highest security. All keys are protected with strong AES-GCM 256 encryption before they are stored, so your credentials are kept safe.

Supported Cloud Providers

• Amazon Web Services (AWS)
• DigitalOcean
• Linode
• Vultr

How to Create a Cloud Auth

Follow these simple steps to connect your cloud account:

1. From the Daestro menu, go to the Cloud Auth page.
2. Click the Add Cloud Auth button.
3. A form will appear. First, choose your cloud provider from the list.
4. Next, enter the API credentials for the provider you chose:
   • For AWS, you will need to enter your Access Key ID and Secret Access Key.
   • For DigitalOcean, Linode, or Vultr, you will need to enter your Access Token.
5. Give the connection a Name you’ll easily recognize, like My Personal AWS Account.
6. Click Save. Your cloud account is now connected!

How to Update a Cloud Auth

You can make changes to a Cloud Auth after you’ve created it.

• You can change its Name at any time.
• You can update the API keys. Important: When updating keys, make sure they belong to the exact same cloud account. Using keys from a different account will cause errors with any services that rely on this connection.

How to Delete a Cloud Auth

If you no longer need a connection, you can delete it. For safety, Daestro will only let you delete a Cloud Auth if no Compute Environments are assocated with it. If you need to delete it, you must first delete associated Compute Environments.