---
title: Installation
description: Get started with Terragrunt Scale - sign up and connect your infrastructure repositories.
slug: terragrunt-scale/installation
sidebar:
  order: 2
---

import { Aside, Steps } from '@astrojs/starlight/components';

This page provides a brief overview of the setup process.

## Getting Started

<Steps>

1. **Sign up** — Create an account at [app.gruntwork.io](https://app.gruntwork.io/signup/terragrunt-scale-free-tier). The rest of the steps listed here will be guided by the onboarding wizard that runs after sign-up.

2. **Connect your VCS** — Install the Gruntwork.io GitHub App or configure a GitLab machine user to connect to one or more Git repositories.

3. **Bootstrap your cloud resources** — Provision all the cloud resources you need to bootstrap your cloud environment for use with Terragrunt Scale. This involves running a single script, then merging a single pull request, generated by the onboarding wizard.

4. **Run your first pipeline** — Click a button in the wizard and have an automatically generated Pull Request (PR) created for you to review and merge. On creation, Pipelines will run a plan, with plan output commented on the pull request. On merge, Pipelines will apply the changes in the PR.

</Steps>

<Aside type="note" title="Custom Installation Guide">

For detailed setup customization options including custom OIDC setups, environment-specific authentication, and advanced options, see the [Gruntwork Pipelines installation guide](https://docs.gruntwork.io/2.0/docs/pipelines/installation/addingnewrepo). This bypasses the automated wizard and has you manually provision all the requisite pieces of Terragrunt Scale yourself. You are encouraged to go through the onboarding wizard first to get familiar with the process.

</Aside>

## Configuration

Terragrunt Scale uses [configuration-as-code defined in HCL](https://docs.gruntwork.io/2.0/reference/pipelines/configurations-as-code/). You can configure settings at the repository, environment, or individual unit level, including:

- Cloud provider authentication (e.g. `aws_oidc` with per-environment plan/apply IAM roles)
- Environment definitions that filter which units a configuration applies to
- Repository-level settings like the branch that deploys IaC (e.g. `main`) and environment variables to set for Terragrunt runs
- Per-unit overrides for authentication and other settings

## Requirements

- A GitHub or GitLab repository you can push to
- An AWS, GCP, or Azure account you can provision infrastructure in

<Aside type="note" title="Free Tier Requirements">

The onboarding wizard for the free tier requires a GitHub repository and an AWS account. [Join the waitlist](https://form.typeform.com/to/c8xJ0vdx) to get notified when GitLab, Azure, and GCP are supported in the free tier.

</Aside>

