Skip to main content

Credentials

Follow the specific cloud and preferred method to create the necessary credentials below:

AWS​

How Massdriver uses your role​

To keep your environment secure, Massdriver uses a role with a trust policy to access your AWS account for provisioning and monitoring of your infrastructure. The account that assumes this role is private and has no access from the public internet.

One click role creation​

Enter a friendly name for your AWS role here:

Click here to run a hosted CloudFormation stack on AWS which will create a new role in your account with the permissions required to provision infrastructure in Massdriver. The external ID for the role (required to prevent confused deputy attacks) will be unique and auto-generated in the URL for the CloudFormation stack. Do not change this value in the URL.

Run the CloudFormation stack​

Once you are in your AWS console, review the resource creation. Click the Create stack button to provision the role.

roles

Import rol to Massdriver​

Once the CloudFormation stack has completed its task, select the outputs tab and copy the value of the CustomProvisioningRoleArn output.

roles

  • Paste the ARN into the AWS ARN field.
  • Set as the Credential Name.
  • Set Loading... as the External ID.

Click Create to add the credential to Massdriver and head to the projects page to start building your infrastructure.

Azure​

Install Azure CLI​

To get started, you'll need the Azure CLI installed locally on your machine. The Azure Cloud Shell available in the Azure Portal does not have the ability to grant the service principal the required permissions.

Enter a friendly name for your Azure service principal here:

  1. Obtain your subscription ID

Paste this script into the command-line to list your subscriptions:

az account list --output table
Enter your Azure subscription ID here:

  1. Paste this script in the command-line to create an Azure service principal:
az ad sp create-for-rbac --name  --role contributor --scopes /subscriptions/
  1. Copy the outputs and paste them into Massdriver:
  • → Credential Name
  • appId → Client ID
  • password → Client Secret
  • → SubscriptionId
  • tenant → Tenant ID

Once finished, click the Create button in Massdriver to create your credential.

GCP​

Create the service account​

Enter a friendly name for your GCP service account here:

Using gcloud CLI, paste the following command in a terminal to create a service account for Massdriver to use:

gcloud iam service-accounts create  --description="Massdriver Service Account" --display-name=

Assign the service account the owner role​

Enter your GCP project ID here:

Paste the following command to assign the service account the owner role:

gcloud projects add-iam-policy-binding  --member=serviceAccount:@.iam.gserviceaccount.com --role=roles/owner

Create a service account key​

Massdriver needs a service account key to access the GCP API. To create one paste the following command into a terminal:

gcloud iam service-accounts keys create md--key.json --iam-account=@.iam.gserviceaccount.com

Attach the .json file created in the above command in to the Artifact Data field on the form.

Set the Credential Name to and click Create to add the credential to Massdriver. Head to the projects page to start building your infrastructure.