Adding a cloud provider

Overview

You can add a cloud provider account to Cloud 66 in one of two ways:

1. During initial app set up (Click the New Application button to get started)
2. Via Account Settings

To add a cloud account via Account Settings:

1. Click on your avatar (top right) and select Account Settings
2. Click on Cloud Platforms in the Settings panel (on the left)
3. Click the + Add Cloud button
4. Add the cloud account details to the drawer that opens from the left
5. Click Add Cloud

Follow the instructions for your preferred cloud provider below to grant Cloud 66 access to your account.

AWS (Amazon Web Services)

First you need to configure your AWS account to allow Cloud 66 to access it:

1. Log into the web interface for your AWS account
2. Click on the name of your account in the top right corner of your AWS account, and select My Security Credentials.

On the next screen, some users will be asked to choose between Security Credentials and IAM users. We support both methods but we recommend that experienced users select IAM (Identity and Access Management) for better security because allows you to set permissions for specific users. Click on your chosen option below for more instructions.

Azure

You can use Cloud 66 to provision and deploy your static site in any Azure region. Cloud 66 needs some credentials to authenticate our agent to provision your infrastructure. You need to specify the following credentials:

• Azure Subscription ID
• Client ID (Microsoft calls this “Application ID”)
• Client Secret
• Tenant ID

You can find those by following the step by step guide created by Microsoft.

Add object storage

For static sites you need to add the Microsoft.Storage Resource provider. To do this:

1. Log into your Azure Portal
2. Click through to the subscription you’re using for Sites
3. Click Resource providers in the left nav
4. Filter the list by the word storage
5. Click on Microsoft.Storage and then the Register button at the top of the panel (it will take a while to react because, Microsoft)
6. Click Refresh after 2 or 3 minutes to check that it is now registered.

For more help read this guide.

Digital Ocean

You can use Cloud 66 to deploy your static site in any DigitalOcean region.

Cloud 66 supports DigitalOcean API v2, which uses OAuth to authenticate requests. If you choose Digital Ocean as a deployment target you'll be redirected to the DigitalOcean Ocean site, where you need to authenticate and approve Cloud 66. Once confirmed you will be redirected back to Cloud 66, where you can deploy your application to your DigitalOcean account.

DigitalOcean Spaces

Static sites run on object storage. As such you will need to grant Cloud 66 access to Spaces Cloud Object Storage in your DigitalOcean account. To do this:

1. Log into your DigitalOcean account
2. Click on API in the left-hand navigation
3. Scroll down to Spaces Access Keys
4. Click Generate New Key
5. Give the key a name and click the tick button
6. Copy the Key ID and Key Secret and paste them somewhere secure
7. Add the Key ID and Key Secret during the next stage of set up (you also need to authenticate via OAuth as described below)

Google Cloud (GCE)

You can use Cloud 66 to deploy your static site in any Google Compute Engine (GCE) region. You need to provide your GCE API keys in order for Cloud 66 to access your account. To generate these:

1. Access the Console of your Google Cloud account
2. Create a project (if you don’t already have one)
3. Switch to your desired project
4. Use the search bar at the top of the page to search for “APIs & Services” and click the first result
5. Click on the blue button (at the top of the main panel) named + Enable APIs and Services
6. Search the API library for “Compute Engine API” and click on the top result
7. If the page does not have a green tick with “API enabled” click the blue Enable button (newer accounts tend to have the API already enabled, but it is worth checking)
8. Return to the “APIs & Services” dashboard (you can use search as you did in step 4)
9. Click on Credentials in the left-hand panel Click on + Create Credentials at the top of the page; Select Service Account
10. Give your service account a name (like “cloud66”) and an optional description; Click Create
11. Add the role “Compute Admin” and then click Continue (NOTE: this will grant Cloud 66 the rights to create/amend/delete compute resources in this project)
12. Leave the User Access options blank and click Done
13. On the Service account details page, click the Keys tab
14. Click Add Key, choose Create new key and select JSON then click Create.
15. Download and save your JSON key somewhere locally (this contains your credentials, so treat it with care)

Once the above is done, we will need three things to connect with your account:

• Email address - this is the email address of the service account you just created (ie. like cloud66@.iam.gserviceaccount.com)
• Project ID - this is your project ID (available at the top of the Overview page)
• JSON key - the file that you downloaded and saved above

Hetzner Cloud

Hetzner does not currently support static site deployments.

Latitude.sh

Latitude.sh does not currently support static site deployments.

Linode

You can use Cloud 66 to deploy your static site in any Linode region.

You need to generate a personal access token for your Linode account to grant Cloud 66 access. To do this:

1. Log into Linode Cloud Manager
2. Click on your username at the top of the screen and select My Profile.
3. Click API Tokens and then Add a Personal Access Token
4. Give the token a label and set its expiry to Never
5. Set the access rights for the token to a minimum of:Account: Read-onlyDomains: Read/WriteKubernetes: Read/WriteLinodes: Read/WriteNodeBalancers: Read/WriteVolumes: Read/Write
6. Click Create Token and then copy the personal access token.

You will use this token to add Linode as a Deployment Target (see below).

OVH

OVH does not currently support static site deployments.

Packet

Packet has been acquired by Equinix and renamed Equinix Metal. As such Cloud 66 no longer supports Packet for new customers, and does not currently support Equinix Metal.

Vultr

Vultr does not currently support static site deployments.