Skip to content

Connect a cloud provider

Let BuildPusher create servers in your DigitalOcean, Hetzner Cloud, Vultr, Linode, AWS (Lightsail or EC2), Google Compute Engine, Azure, OVHcloud, Scaleway or UpCloud account.

1Create a token at the provider

In your provider’s dashboard, create an API token with read and write access.

2Add it here

Account → Providers → Connect a provider. Choose the provider, paste the token and save. We check it straight away. You can also connect one without leaving the page you’re on: the new server form, a new repository and Start from a template each offer Connect a provider, and pick it up once it’s saved.

3Credentials that aren’t one token

AWS Lightsail takes an access key as ACCESS_KEY_ID:SECRET_ACCESS_KEY. Scaleway takes the project ID and an API secret key as PROJECT_ID:SECRET_KEY; servers go in that project and its SSH keys are added to them. UpCloud takes an API user (Account → People, with API access) as USERNAME:PASSWORD. Scaleway, UpCloud and OVHcloud prices are shown in euros.

4AWS EC2, Google Cloud and Azure

AWS EC2 takes an access key as ACCESS_KEY_ID:SECRET_ACCESS_KEY for an IAM user allowed EC2 actions; servers go in the region’s default VPC with a “buildpusher” security group for SSH, HTTP and HTTPS. Google Compute Engine takes a service account’s JSON key (paste the whole file) with the Compute Instance Admin and Compute Security Admin roles; servers go in that project’s default network. Azure takes a service principal with Contributor on the subscription as TENANT_ID:CLIENT_ID:SUBSCRIPTION_ID:CLIENT_SECRET; each server gets its own resource group, removed with the server. Prices shown are on-demand list prices in us-east-1, us-central1 or East US; Costs shows what AWS actually charged.

5OVHcloud

Create an API application and a consumer key allowed GET, POST and DELETE on /cloud/project/*, then enter ENDPOINT:APPLICATION_KEY:APPLICATION_SECRET:CONSUMER_KEY:PROJECT_ID, with eu or ca as the endpoint and your Public Cloud project’s ID. Instances are billed by the hour.

6GitHub App

Where the GitHub App is available, choose Install the GitHub App on Account → Providers and pick the repositories it may reach. Its repositories are listed for you to connect, pushes deploy without a webhook to set up, and previews get a check run and a comment on the pull request.

7Source control and DNS

GitHub, GitLab, Bitbucket and DNS providers (Cloudflare, Hetzner DNS and AWS Route 53, whose credential is ACCESS_KEY_ID:SECRET) are added the same way, from the same page. A DigitalOcean provider manages DigitalOcean DNS too.

Still stuck?Email us, or send feedback from inside the app.