Reading time: 2 minutes
Before using Scalr to run Terraform there are typically a few quick things you need to set up.
Cloud Credentials - Add authentication for the cloud Terraform providers which will be injected as environment variables into workspaces.
VCS Providers - Connect Scalr to your VCS for automated runs (we support all the most commonly used ones)
Grant Access - Invite users, create teams and grant access through IAM.
Environments - Create environments to host your workspaces in logically related groups.
Workspaces - This is where Terraform runs. Connect a workspace to VCS for automated runs, or use them as a backend for the CLI.
At the Account scope.
Cloud credentials can be linked to environments so that the appropriate environment variables are injected into the workspaces for the associated provider. For example, if you add credentials for AWS you will get these variables in the workspaces.
You can have multiple sets of credentials with different ones linked to different environments.
See Cloud Credentials for details of setting up credentials for the major cloud providers.
At account or environment scope you can add a VCS provider connection.
See VCS Providers for full details of configuring each type of VCS provider.
At the Account scope (green)
Users and teams are assigned access policies to give them permissions to access environments and workspaces.
Invite additional users
Create teams to enable collaboration
Grant access via access policies.
See Identity and Access Management for full details on granting access to Scalr.
Environments are collections of related workspaces that correspond to functional areas, SDLC stages, projects, or any grouping that is required.
The environment is where you can assign policies, credentials, registry modules, registry templates, and VCS providers that will then be available or enforced on every workspace in that environment.
All items placed at the account scope can be optionally shared across environments.
Workspaces within an environment are where Terraform configurations are run to deploy infrastructure, and where state files are stored.
At the account scope
Create environments as required
Grant access policies to enable user and team access.
Link any cloud credentials that are required.