> ## Documentation Index
> Fetch the complete documentation index at: https://docs.maia.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Setup guide - Matillion Full SaaS Amazon Redshift

export const maia = "Maia";

This document describes the necessary steps to follow to set up your first working project in {maia} for the following configuration options:

<div class="metadata-grid" data-search-exclude>
  <div class="metadata-label">Deployment type:</div>

  <div class="metadata-value">
    <span class="cdp">Matillion Full SaaS</span>
  </div>

  <div class="metadata-label">Cloud platform:</div>

  <div class="metadata-value">
    <span class="cdp">Provided by Matillion</span>
  </div>

  <div class="metadata-label">Cloud data warehouse:</div>

  <div class="metadata-value">
    <span class="cdp">Amazon Redshift</span>
  </div>
</div>

***

## Prerequisites

### Amazon Redshift requirements

* An [Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/welcome.html) account with the following information:
  * The physical address of the Amazon Redshift leader node. This will be either a name or an IP address.
  * The port Amazon Redshift communicates on, configured when setting up your Amazon Redshift cluster.
  * Your Amazon Redshift username and password.

### Connectivity requirements

* Access enabled for the IP addresses listed under the **Full SaaS** section of [Network access and IP Allowlist requirements](/docs/security/network-access-and-ip-allowlist-requirements/#full-saas).

***

## Setup steps

1. Register for a [{maia} account](/docs/administration/registration).
2. [Create accounts](/docs/administration/manage-other-users) for users and admins who will be active in {maia}.
3. Create a [project](/docs/guides/projects#add-a-new-project), making the following choices:
   * Select **{maia} managed**.
4. Create an [environment](/docs/guides/environments) using your Redshift credentials.
5. Set up [secret definitions](/docs/guides/secrets-and-secret-definitions) for passwords, API keys, and tokens.
6. Create a Git [branch](/docs/guides/branches) in which to begin pipeline work.
7. Create your first [pipeline](/docs/guides/pipelines).