Cloud Credentials

Reading time: 2 minutes

This page explains how to set up the Terraform provider credentials in Scalr so that they are automatically propagated to workspaces.

Many Terraform providers support the use of shell variables to pass credentials. Scalr exploits this feature to automatically propagate shell variables to workspaces from a centrally configured Cloud Credentials page.

Note

All credentials are stored and encrypted using AES 256. Not all Terraform providers support the use of shell variables for credentials. Check the documentation for the each provider in the configuration.

Configuring Credentials

Configuring cloud credentials directly in Scalr is a three step process.

1. Set up necessary authentication in the cloud provider (varies from cloud to cloud).

2. Create Cloud Credentials in Scalr in the account (green).

   

3. Link Cloud Credentials to the required environments:

   

Environments can be linked to multiple clouds, but there can only one set of credentials per cloud type per environment.

Scalr currently supports cloud credentials for the following providers. Click the links for guidance on configuring access in these clouds.

• AWS Credentials
• Azure Credentials
• Google Cloud Credentials
• VMware Credentials

Credentials for other providers can be added manually to workspaces by adding environment variables via the Variables tab, or via the scalr_variable resource of the Scalr Terraform Provider.

Using Cloud Credentials

This screen shot shows some example variables for Azure, AWS and GCP in a workspace.

With credentials set up this way the Terraform configuration can now include provider blocks that omit the credentials parameters as shown in this AWS example.

provider "aws" {
  region     = var.region
}