Skip to main content
Run SignuDoc’s document signing app from a GitHub repository, with PostgreSQL in your AWS account. This guide covers the container build, protected first-run setup, email delivery and the checks to complete before you send an agreement.
This guide uses local file storage. Spring Winter task files and service-managed EBS task volumes are temporary. The deployment test kept envelope records after task replacement, but the uploaded PDF returned 404. Use disposable documents on task compute. For documents you need to keep, run the app on a host with a persistent filesystem and backups.

Create with an agent

Copy agent prompt

Before you start

Connect AWS and GitHub to Spring Winter. Prepare a repository you control and choose the AWS Region for your project. The November 18, 2026 test used upstream commit d80866c, after release v0.4.0. Upstream did not include a Dockerfile or a prebuilt application image for that test. Check the selected release before you prepare your copy. SignuDoc source.

Prepare the container

Add the following Dockerfile to your repository root. It follows the build used in the deployment test. Keep the upstream package-lock.json committed.
Download the public RDS global CA bundle from AWS and commit it at certs/rds-global-bundle.pem. Verify that the file is tracked and included in the build context. The container uses it to trust the RDS server certificate. AWS certificate bundles. Add a .dockerignore file so local data and credentials stay outside the image.
Supply database credentials at runtime. The startup command applies pending migrations before the HTTP server starts. A failed migration stops startup. Review schema changes and backups before upgrading an installation with existing documents.

Create the database and web server

Create a private SQL database with PostgreSQL. Wait for its provisioning workflow to succeed, then use Connect to obtain the writer endpoint and credentials. The test used standard RDS PostgreSQL 18.3, db.t4g.micro, 20 GiB of gp3 storage and one-day backup retention in us-east-1. Check the regional catalog before selecting those values. Choose backup retention for the installation you are creating. Create a web server from your connected repository. Leave the container command override empty so the Dockerfile starts the app. This sizing is a tested starting point. Measure PDF processing and memory use with your expected documents. The test’s first probe, /accessibility, returned 404 outside hosted mode. The root and login pages can redirect. Use /api/auth/ok, then verify database and document operations separately.

Configure runtime variables

Set these in Environment → Runtime. Keep secret values out of Git, build variables and copied prompts. Set SETUP_TOKEN before creating public compute. After creation, read the returned public_url and use it for APP_URL. If you already have a confirmed custom HTTPS URL, use that address. Verify the final URL before setup or sending invitations. A runtime save can replace the task. Through the API, environment PUT replaces the full variable list for its scope. Merge changes in memory and preserve the other variables. Environment variables. Keep EMAIL_DRIVER unset for Resend delivery. The development capture driver is refused on a production HTTPS installation. Leave HOSTED_MODE unset for an installation belonging to one organization.

Complete setup and email delivery

Open /setup over HTTPS. Enter the setup token, organization details, support address and first administrator account. After setup, confirm that the setup page redirects to login and that the administrator can sign in. In Settings → Organization, configure the sending address and verify its domain through Resend. Use an approved address you control for the first invitation. The deployment test omitted Resend. Uploading and preparing an envelope worked, but sending returned 503, “Email is not set up yet”. Email is required to deliver the signing links. Test sending and signing before inviting your team.

Schedule daily cleanup

Configure an approved scheduler to send a GET or POST request once a day to /api/internal/retention. Send the RETENTION_JOB_SECRET value as a bearer token in the Authorization header, using the scheduler’s secret store. Spring Winter does not run the cron configuration in vercel.json. The retention job also handles due reminders and expired envelopes. Verify the scheduler’s response and execution history. Upstream scheduled work.

Verify before sending agreements

Use a non-sensitive PDF and an email recipient you control.
  1. Wait for the workflow to succeed and confirm /api/auth/ok returns HTTP 200.
  2. Complete protected setup and sign in. Open the dashboard and settings.
  3. Upload the PDF, add a signer and place signature and date fields.
  4. Confirm the permitted-use declaration when sending. Verify invitation delivery, finish signing and download the completed PDF.
  5. Export the audit trail and check the app’s verification page.
  6. If the plan includes a replacement test, confirm the new task is serving alone before checking records and files again.
For a persistent local deployment, back up both PostgreSQL and the complete storage directory, including metadata files. Verify recovery into a disposable target. A database backup alone cannot recover the PDFs lost from a task. Review current AWS estimates before deployment. Include database compute and storage, Fargate, builds, load balancing, public IPv4, logs and any external host or email charges. Use project costs to inspect billed usage after AWS reports it.