> For the complete documentation index, see [llms.txt](https://docs.infraglide.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraglide.com/getting-started/quickstart.md).

# Quickstart Guide

This guide walks you from first sign-in to a deployed infrastructure stack in InfraGlide. By the end, you will have configured your organization context, selected a Workspace and Sandbox, added a cloud credential, created a pipeline, and executed a successful Terraform run.

***

## 📋 Before You Begin

You will need:

* 🔐 An **InfraGlide account** (sign-in is handled securely through Auth0 or Google SSO).
* ☁️ Access to at least one cloud provider account (**AWS**, **Azure**, or **GCP**) with administrative permissions to provision resources.
* 🏢 An **Organization membership**. Organization context is resolved automatically from your signed-in identity.

{% hint style="info" %}
If your organization has not completed setup yet, an **Org Admin** should complete the onboarding wizard first (Settings → **Organization Setup**).
{% endhint %}

***

## 🏢 Step 1: Complete Organization Onboarding (Org Admins)

Org Admins walk through a guided setup wizard to configure the foundational structure:

1. **Welcome** — Overview of the setup flow.
2. **Workspaces** — Create top-level team or business-unit areas (e.g., *Platform Engineering*).
3. **Sandboxes** — Create target environments (e.g., `dev`, `staging`, `prod`) inside each Workspace.
4. **Credentials** — Add the initial cloud credentials for your Sandbox.
5. **Cloud APIs** — Verify enabled cloud provider APIs.
6. **Storage** — Configure artifact storage for pipeline deployment outputs.
7. **Git Sync** — Optional Hub and Git repository synchronization.
8. **Finish** — Finalize organization setup.

<figure><img src="/files/HDWxqu8Nm8nRPXuJT7u2" alt="Organization Onboarding Welcome"><figcaption><p>Figure 1: Organization Onboarding Welcome Screen</p></figcaption></figure>

<figure><img src="/files/J0PfhxiEQerE9MICfFjR" alt="Workspaces Onboarding Step"><figcaption><p>Figure 2: Creating Workspaces during onboarding</p></figcaption></figure>

<figure><img src="/files/BM7uzpTF1qJuJU6IBsQE" alt="Sandboxes Onboarding Step"><figcaption><p>Figure 3: Setting up Environment Sandboxes</p></figcaption></figure>

<figure><img src="/files/UROuwaBxGQYD2PI5HWOQ" alt="Cloud APIs Onboarding Step"><figcaption><p>Figure 4: Verifying Cloud Provider APIs</p></figcaption></figure>

<figure><img src="/files/Kf3to57RKO8qOT3SDbUX" alt="Storage Onboarding Step"><figcaption><p>Figure 5: Artifact &#x26; Storage Configuration</p></figcaption></figure>

<figure><img src="/files/hKkHspeEV3zeS8QHCZ0H" alt="Git Integration Onboarding Step"><figcaption><p>Figure 6: Git &#x26; Hub Sync Setup</p></figcaption></figure>

<figure><img src="/files/qXQhWtzDsLPy9Kv64mhz" alt="Onboarding Complete"><figcaption><p>Figure 7: Finalizing Organization Onboarding</p></figcaption></figure>

{% hint style="success" %}
Non-admin users skip this wizard when Workspaces and Sandboxes already exist and can immediately select their assigned environment in the header.
{% endhint %}

***

## 🎯 Step 2: Select a Workspace and Sandbox

In the top navigation header, open the environment dropdown and select the **Workspace / Sandbox** pair you will work in.

<figure><img src="/files/TxBC8CrqJ04rgUOfRtH3" alt="Select Workspace and Sandbox"><figcaption><p>Figure 8: Selecting Workspace and Sandbox in the Header Dropdown</p></figcaption></figure>

* **Scope Isolation**: Pipelines and credentials always belong to a Sandbox.
* **Context Switching**: Switching Sandboxes updates which pipelines, credentials, and deployment metrics are visible.

{% hint style="warning" %}
If the selector dropdown is empty, ask an Org Admin or Workspace Admin to grant you access to a Workspace or create a Sandbox for your team.
{% endhint %}

***

## 🔑 Step 3: Add a Cloud Credential

Open **Administration → Credentials** (or complete the Credentials step during onboarding).

<figure><img src="/files/G28efpUAUDHSORWbkOdo" alt="Add Cloud Credential Form"><figcaption><p>Figure 9: Adding a new Cloud Credential for AWS, Azure, or GCP</p></figcaption></figure>

<figure><img src="/files/d216n8RQetNjurA8lK2m" alt="Cloud Credentials Configuration"><figcaption><p>Figure 10: Configuring Credential Parameters &#x26; Permissions</p></figcaption></figure>

Create a credential for your active Sandbox:

| Provider  | Authentication Method   | Required Fields                                           |
| --------- | ----------------------- | --------------------------------------------------------- |
| **AWS**   | Access Keys or IAM Role | Access Key ID + Secret Key, **or** Role ARN + External ID |
| **GCP**   | Service Account Key     | Service Account JSON File / Key String                    |
| **Azure** | Service Principal       | Client ID, Client Secret, Tenant ID, Subscription ID      |

Use **Test Connection** to verify API access before saving. Secret keys are encrypted immediately and are never exposed back to the browser.

***

## 🏗️ Step 4: Create Your First Pipeline

Navigate to **Build & Deploy → My Pipelines** and click **+ New Pipeline**.

### 📖 Option A — Start from a Template

1. Open **Build & Deploy → Templates**.
2. Pick a production-ready reference architecture for AWS, Azure, or GCP.
3. Confirm your target Sandbox and click **Create Pipeline**.

### 🎨 Option B — Start from a Blank Canvas

1. Click **+ New Pipeline** from **My Pipelines**.
2. Name your pipeline and select your cloud provider (AWS, Azure, GCP).
3. The visual canvas opens with the **Component Library** on the left.

***

## 🎨 Step 5: Design on the Visual Canvas

1. **Drag Components**: Drag resources from the left Component Palette (e.g. VPC, Subnets, EC2 Instances, S3 Buckets) onto the canvas grid.
2. **Container Nesting**: Drop child resources inside container nodes (e.g., placing an EC2 Instance inside a Subnet) to automatically inherit location and network attributes.
3. **Connect Nodes**: Draw connection lines between nodes to establish explicit dependencies.
4. **Edit Attributes**: Click on a node to open the right-hand **Properties Panel** and configure parameters.
5. **Save Draft**: Click **Save** in the top toolbar to record your canvas state.

<figure><img src="/files/p85vX5ZJkGESj9jJjzHL" alt="Designer Canvas Overview"><figcaption><p>Figure 10: Visual Pipeline Architecture Canvas</p></figcaption></figure>

***

## 🔍 Step 6: Attach Credential & Preview (Plan)

In the designer top toolbar:

1. Select your target credential from the **Credential** dropdown.
2. Click **Preview** to run an asynchronous Terraform `plan` without modifying live cloud infrastructure.

<figure><img src="/files/YmtpOkD9ySpCyNkv1Wqf" alt="Designer Toolbar Actions"><figcaption><p>Figure 11: Designer Toolbar Split Buttons (Preview, Deploy, Destroy)</p></figcaption></figure>

Running **Preview** is recommended before applying changes. It allows you to verify resource changes, additions, and syntax before live provisioning.

***

## 🚀 Step 7: Deploy Infrastructure

1. Click **Deploy** in the top toolbar.
2. Review deployment parameters and click **Start Deployment**.
3. InfraGlide generates standard Terraform JSON configurations, dispatches the job to background workers, and streams logs in real time.

<figure><img src="/files/GDHa3XfOoiQQj7hJoXAe" alt="Live Deployment Execution Logs"><figcaption><p>Figure 12: Real-time Execution History and Streaming Output Logs</p></figcaption></figure>

Once finished, the run status will update to **Success**. You can inspect granular per-resource status badges in the **Executions** panel.

***

## ⚡ Step 8: Verify & Iterate

* **Deployed Inventory**: Open **Operations → Deployed Resources** to inspect live infrastructure linked to your Sandbox.
* **Drift Detection**: Use **Check Drift** from the pipeline menu to scan for out-of-band manual changes in your cloud provider console.
* **Teardown**: To decommission resources, click **Destroy** in the toolbar and type `destroy` in the confirmation dialog.

<figure><img src="/files/UZFx4RpEBsKFFVHkjNqT" alt="Pipeline Check Drift Menu"><figcaption><p>Figure 13: Pipeline Check Drift Menu Control</p></figcaption></figure>

***

## 🛠️ Common Troubleshooting Steps

| Symptom                            | Likely Cause                             | Solution                                                  |
| ---------------------------------- | ---------------------------------------- | --------------------------------------------------------- |
| Deploy button disabled             | No credential linked to pipeline         | Attach a credential in the designer top toolbar           |
| Empty Workspace / Sandbox selector | No workspace access assigned             | Ask an Org Admin to invite you or create a Sandbox        |
| Provider tab disabled in Library   | Organization provider policy restriction | Ask an Admin to enable the provider in Settings           |
| Concurrent deployment error        | Another `Plan` or `Apply` run is active  | Wait for the active execution to complete before retrying |

***

## What's Next?

* Understand nested scopes in [Core Concepts & Terminology](/getting-started/core-concepts.md).
* Explore designer toolbars in [Designer Interface Overview](/visual-canvas-and-pipeline-designer/interface-overview.md).
* Learn about failure diagnosis in [Deployment Error Analysis](/jane-ai-copilot/error-analysis.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.infraglide.com/getting-started/quickstart.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.