Cloud Deploy

Deploy static and frontend applications from GitHub to AWS with managed infrastructure.

Deploy static and frontend applications from GitHub to AWS. Cloud Deploy builds your app on a managed build runner and serves it via S3 and CloudFront.

What is Cloud Deploy?

Cloud Deploy lets you connect a GitHub repository to an AWS account and deploy your static or single-page application (SPA) with a few steps. Orkestia provisions the per-site infrastructure (S3 bucket, CloudFront distribution) and runs your build pipeline on a managed build runner in your own cloud on each deploy.

AWS is the most mature, fully documented target for Cloud Deploy. The product can also target other clouds (GCP, Azure, Cloudflare); see the workflow reference for the spad.* workflows behind each provider.

Benefits

GitHub to AWS

Connect a repo and branch; deploy on push or on GitHub releases.

Managed Infrastructure

S3 and CloudFront are created and managed for you; builds run on a managed build runner.

Build Pipelines

Configure install and build stages (e.g. npm install, npm run build) that run on a managed build runner.

Custom Domains

Add your own domain with automatic SSL (requires a DNS connection).

Rollback

Roll back to a previous deployment from the site dashboard.

Deployment History

View logs, status, and duration for every deployment.

Prerequisites

Before using Cloud Deploy, your organization must have:

An AWS Connection - So Orkestia can create and manage resources in your AWS account. See AWS Connections.
A GitHub Connection - So Orkestia can access your repositories and (optionally) receive webhooks for auto-deploy.

A DNS connection is optional and only needed if you want to use custom domains on your site.

How It Works

flowchart TB subgraph step1["Step 1: Create Site"] A1["Choose AWS + GitHub"] A2["Pick repo & branch"] A3["Set build config"] A1 --> A2 --> A3 end subgraph step2["Step 2: Provision"] B1["Infrastructure<br/>(S3, CloudFront)"] end subgraph step3["Step 3: Deploy"] C1["Build → Upload → Invalidate<br/>(or auto on push)"] end D["Optional: Custom domains<br/>(DNS connection required)"] step1 --> step2 step2 --> step3 step1 -->|Trigger deploy| step3 step3 --> D

Site Statuses

Status	Description
Provisioning	Infrastructure (S3, CloudFront) is being created
Active	Site is ready; you can trigger deployments and add custom domains
Failed	Infrastructure provisioning failed; use Retry or Check from the site page

Quick Links

Getting Started

Prerequisites and opening Cloud Deploy.

Creating a Site

New site wizard with connections, repository, and build config.

Site Overview

Site detail, trigger deploy, and rollback.

Deployment Progress

Progress page, logs, and success page.

Settings

Name, branch, build stages, and env vars.

Custom Domains

Add, verify, and manage custom domains.

Resources & Releases

AWS resources, releases, and delete site.

Admin Dashboard

Sites timeline and events for org admins.

Troubleshooting

Common issues and solutions.

Troubleshooting

Solutions for common DNS connection issues.

Getting Started

Prerequisites for Cloud Deploy and how to open it in Orkestia.