Skip to main content
Springwinter gets you from zero to a live, AWS-hosted service in under ten minutes. This guide walks you through every step — creating an account, linking your AWS account and GitHub repository, and watching your first deployment go live. By the end you will have a real ECS service or CloudFront-backed static site running inside your own AWS account.
Before you begin, make sure you have:
  • An AWS account with permissions to create CloudFormation stacks and the resources Springwinter needs (ECS, RDS, S3, etc.).
  • A GitHub account with at least one repository that contains either a Dockerfile (for web servers and workers) or a static build output directory (for static websites).
  • About 10 minutes — that’s genuinely all it takes.
1

Create your Springwinter account

Open https://springwinter.dev/auth?mode=signup and sign up with Google, Microsoft, or your email address. After you confirm your email, you land on the Springwinter dashboard.
2

Connect your AWS account

Springwinter deploys resources into your AWS account using a CloudFormation-provisioned IAM role — no long-lived credentials are ever stored. In the dashboard, open Settings → AWS and click Connect AWS. Springwinter generates a CloudFormation link that creates the required role in your account.Follow the full walkthrough in Connect Your AWS Account, then return here once your Role ARN is verified.
3

Connect your GitHub account

Open Settings → GitHub and click Connect GitHub. You are redirected to the GitHub App installation page where you choose which repositories Springwinter can access. After you confirm the installation, you are returned to the dashboard automatically.See Connect GitHub for details on permissions and multi-organization setups.
4

Create a project

In the dashboard, click New Project, give it a name, and confirm. Projects group your related services together and share the same AWS connection and team members. Every resource you create lives inside a project.
5

Add a web server or static website

Inside your new project, click Add Resource and choose the resource type that matches your repository:
  • Web Server — your repo has a Dockerfile and exposes an HTTP port.
  • Static Website — your repo produces an index.html (React, Next.js export, Astro, plain HTML, etc.).
Select the GitHub repository and branch, set any environment variables you need, and click Deploy. Springwinter kicks off the first build immediately.
6

Watch the build and visit your live URL

The dashboard streams your build logs in real time. For a web server, Springwinter builds your Docker image, pushes it to ECR, and rolls it out on ECS behind a load balancer with a TLS certificate. For a static website, it uploads the build output to S3 and provisions a CloudFront distribution.When the status indicator turns green, click the URL shown on the resource card — your service is live.
Auto-deploy is enabled by default. Every push to the branch configured on your resource triggers a new build and rolls out the updated version automatically. No CI configuration required.

​
What to do next

Web Servers

Configure scaling, health checks, custom domains, and environment variables for containerized services.

Workers

Deploy background processing services that run alongside your web servers without a public endpoint.

Static Websites

Customize your CloudFront distribution, set up redirects, and configure build commands.

Observability

Explore CloudWatch logs, CPU and memory metrics, request rates, error rates, and live cost estimates.