Cloud Deploy
Creating a Site
Walk through the New Site wizard to create a Cloud Deploy site.
This guide walks you through the New Site wizard: choosing connections, repository, and build configuration.
Overview
The New Site wizard has three steps:
- Connections - Select an AWS connection and a GitHub repository
- Repository - Set site name, branch to deploy, and deployment trigger
- Build config - Set framework, build stages, output directory, and Node version
You can move between steps with Next and Back. The Create site button is enabled only when all steps are valid.
Prerequisites
- An AWS connection and a GitHub connection (organization-wide, active)
- The GitHub connection must have at least one repository available
Step 1: Connections
Open the wizard
From the Cloud Deploy list (/apps/spad), click New Site (or Create site).
Select Cloud Connection
Choose an active AWS connection from the list. This is the account where the site will be deployed (S3, CloudFront) and where builds run.
Select GitHub Repository
Choose the repo that contains your app from the dropdown. If no repos appear, check that your GitHub connection is active and has access to the repositories you expect.
Proceed to next step
Click Next to go to Step 2.
Step 2: Repository
| Field | Description |
|---|---|
| Site Name | A short name for the site (e.g. my-awesome-site). Used in URLs and labels. May be pre-filled from the repository name. |
| Branch to Deploy | Choose the branch to build and deploy (e.g. main, develop). The list is loaded from the selected repository. |
| Deployment Trigger | When deployments run - either on branch push or on GitHub release. |
Deployment Trigger Options
- Deploy on branch - Deploy when code is pushed to the selected branch (optional: enable/disable auto-deploy)
- Deploy on release - Deploy when a GitHub release is published (optional: action type and whether to include prereleases)
Click Next to go to Step 3.
Step 3: Build Config
| Field | Description |
|---|---|
| Framework | Optional preset (React, Vue, Nuxt, Next.js, etc.) or "Auto-detect / Other". Presets pre-fill build command and output directory. |
| Build Stages | Ordered steps run during each deployment. Typically an Install stage and a Build stage. |
| Output Directory | The folder containing the built static files (e.g. dist, build, out, .output/public). |
| Node Version | Node.js version for the build (e.g. Node 18 LTS, Node 20). |
Build Stages
- Typically an Install stage (e.g.
npm install,yarn install,pnpm install) and a Build stage (e.g.npm run build) - You can add more stages, reorder them, enable/disable each stage, and pick from detected npm scripts
- At least one enabled stage with a command is required
Review all fields, then click Create site.
After Creating the Site
- The site is created and infrastructure (S3, CloudFront) starts provisioning
- You are redirected to the site detail page (
/apps/spad/{site-uuid}) - On the site page you can:
- See status (e.g. Provisioning, then Active when ready)
- Trigger a deployment once the site is Active
- Open Settings to change options later
See Site Overview for what to do next after creating your site.