AWS

Run launch-stack.sh

launch-stack.sh is a genuine one-command launch: it resolves the newest server-v* release itself (or a version you pin), downloads and checksum-verifies the published CloudFormation template from that release, validates it, and runs aws cloudformation deploy with your AWS CLI credentials. Inspect it first, then run it:

curl -fsSLO https://raw.githubusercontent.com/proliferate-ai/proliferate/main/server/infra/self-hosted-aws/launch-stack.sh
less launch-stack.sh
bash launch-stack.sh --site-address proliferate.company.com

No domain to test with yet? bash launch-stack.sh --eval launches with no SiteAddress at all; the stack derives a hostname from the Elastic IP (<ip>.sslip.io) and still gets real Let's Encrypt TLS.

Prefer the AWS Console, or need parameters launch-stack.sh doesn't expose as flags yet? See Launch from the console below — same template either way.

Wait for CREATE_COMPLETE

Bootstrap runs automatically on first boot. The stack sets PROLIFERATE_PUBLIC_HEALTHCHECK_URL itself, so CloudFormation only reaches CREATE_COMPLETE once the advertised HTTPS endpoint actually responds (20-minute timeout). launch-stack.sh waits on this for you; from the console watch the stack's Events tab.

Stack outputs:

Get the setup token and claim your instance

Run the command from the ReadSetupTokenCommand output (aws cloudformation describe-stacks --stack-name proliferate-self-hosted, or read it off the console's Outputs tab). It opens an SSM session that prints the one-time setup token and exits:

aws ssm start-session --target <InstanceId> \
  --document-name AWS-StartInteractiveCommand \
  --parameters '{"command":["sudo docker exec $(sudo docker ps -qf name=api) cat /var/lib/proliferate/setup/setup-token"]}'

The token also appears in /var/log/cfn-init-cmd.log on the host, and you can always reprint it with the Docker flow's health gate: open a shell with the SsmStartSessionCommand output, then cd /opt/proliferate/server/deploy && sudo ./wait-for-health.sh.

Open the SetupClaimUrl output in a browser and enter an email, a password, an optional organization name (blank derives one from your email domain), and the token. That account becomes the owner of the instance organization, and the page returns 404 forever after.

Work from a browser, or connect the desktop app

The stack's BaseUrl already serves the Web app: sign in there to work. If you or your teammates need local repositories or a local AnyHarness runtime, also point the desktop app at BaseUrl. See Connect the desktop app.

Launch the template

Launch the CloudFormation template (server/infra/self-hosted-aws/template.yaml, published with each server-v* release) and fill in the stack parameters. For a production install, set SiteAddress and point DNS at the Elastic IP (or let the stack do it with CreateRoute53Record). For a quick evaluation, set UseSslipFallback to true and leave SiteAddress blank.

The template is a template-body-eligible size, so the CLI equivalent works directly with no S3 upload step:

aws cloudformation create-stack \
  --stack-name proliferate-self-hosted \
  --template-body file://template.yaml \
  --capabilities CAPABILITY_IAM \
  --parameters ParameterKey=UseSslipFallback,ParameterValue=true