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 prefered cloud provider below to grant Cloud 66 access to your account.

AWS (Amazon Web Services)

Cloud 66 supports both VPC and (for AWS accounts created before 2014) EC2-Classic. We also support reserved instances. To use a VPC, your account must conform with the default VPC guidelines.

You need to configure AWS so that Cloud 66 to access your account. To to this:

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.

Help with advanced AWS features:

• Using IAM instance profiles with your servers
• Cloud 66 Security Groups on AWS
• AWS Reserved instances
• Using AWS EC2-Classic
• Cloud 66 tag propagation

Azure

You can use Cloud 66 to provision and deploy your code to servers 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 Prepress
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.

Help with advanced Azure features:

• Cloud 66 tag propagation

Digital Ocean

You can use Cloud 66 to provision and deploy your code to servers (droplets) in any DigitalOcean region.

Private networking is enabled for all data centers that support it. This means that servers can communicate freely between each other on the same network without counting towards bandwidth costs.

Cloud 66 supports DigitalOcean API v2, which uses OAuth to authenticate requests. If you choose Digital Ocean as a deployment target (see below) 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.

Help with advanced Digital Ocean features:

• Bring Your Own Images (BYOI)
• Cloud 66 tag propagation

Google Cloud (GCE)

You can use Cloud 66 to provision and deploy your code to servers 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

Help with advanced GCE features:

• Using GCE service accounts with Cloud 6
• Bring Your Own Images (BYOI)
• Cloud 66 tag propagation

Hetzner Cloud

You can automatically provision and deploy to Hetzner Cloud servers in any supported location via Cloud 66. You need to add a Hetzner Cloud API key to your Cloud 66 account in order to integrate them. On Hetzner API keys are specific to “projects”. To generate an API key:

1. Log into your Hetzner Cloud dashboard
2. Either add a new project or click on an existing one
3. Click on the key (Access) in the left-hand navigation
4. Click on API Tokens at the top of the main panel
5. Click the Generate API Token button (top right) and give your token a name (e.g. Cloud 66)
6. Copy the API token and save it somewhere (it won’t ever be shown again by Hetzner)

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

Help with advanced Hetzner Cloud features:

• Cloud 66 tag propagation

Latitude.sh

You can automatically provision and deploy to Latitude.sh bare metal servers in any supported location via Cloud 66. You need to add create a Latitude.sh API key in order to connect it to Cloud 66:

1. Log into your Latitude.sh dashboard
2. Click on API in the left-hand navigation
3. Click the Create Key button (top right) and give your token a name (e.g. Cloud 66)
4. Copy the API token

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

Help with advanced Latitude.sh features:

• Cloud 66 tag propagation

Linode

You can use Cloud 66 to provision and deploy your code to servers in any Linode region. Private networking is automatically enabled for all servers deployed by Cloud 66. This means that servers can communicate freely between each other on the same network without counting towards bandwidth costs.

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).

Help with advanced Linode features:

• Cloud 66 tag propagation

OVH

You can automatically provision and deploy to OVHcloud servers in any supported location via Cloud 66. We use Project IDs to access to your cloud resources on OVHcloud. To enable Cloud 66 to manage your servers you need to:

1. Create a new Project using your OVHcloud dashboard (or open an existing one)
2. Open the Project and click on Private Network (in the left nav) and then Create a vRack
3. Choose New vRack and then click *Create (*wait for the vRack to be set up before moving on).
4. Copy the Project ID (at the top left, just below your project’s name
5. You will use this token to add OVH as a Deployment Target (see below).
6. After you paste in your Project ID and click Add Cloud. you will be taken to a sign-in page on the OVH site where you can confirm the required permissions and then log in to authenticate Cloud 66’s access to your Project.

Help with advanced OVHcloud features:

• Using multiple keys with OVH

Packet

You can use Cloud 66 to provision and deploy your code to servers in Packet.

Help with advanced Packet features:

• Cloud 66 tag propagation

Rackspace

You can use Cloud 66 to provision and deploy your code to servers in any Rackspace region. You need to provide your Rackspace API key in order for Cloud 66 to access your account. To generate a key:

1. Log into the Rackspace web interface
2. Click the Account dropdown in the top right
3. Go to the User Management page
4. Click Create a new user, and fill in the necessary details for this new user. This user must be created with Full Access in order for servers to be created in your account.
5. Once you click Create user, you will be able to view the API Key by clicking Show.

You will use this key to add Rackspace as a Deployment Target (see below).

Vultr

You can automatically provision and deploy to Vultr servers in any data centre via Cloud 66. You need to add your Vultr API key to your Cloud 66 account in order to integrate them. To generate a Vultr API key:

1. Click on your account dropdown (top right) and select API
2. Enable API access (if it’s not enabled already)
3. Update the Access Control list to allow access from “Any IPv4” and “Any IPv6”. If you would prefer to restrict access, you will need to add each of Cloud 66’s authorized IP addresses individually.
4. Copy your new Vultr API key

You will use this key to add Vultr as a Deployment Target (see below).