Create a web server
Choose a name and source. For a repository, select a repository and set the Dockerfile path. For an image, provide a public image reference. Set the container port and a health path. The load balancer probes the container over HTTP. Choose a path that returns HTTP 200 on that port without login or redirects, including when the public site uses HTTPS. Choose CPU, memory, and task-copy settings for the service. Spring Winter builds and deploys the service. The load balancer sends requests to healthy tasks. If deployment fails, open History to review the run and its error before you redeploy. If the health wait reaches its five-minute limit, check application logs for slow startup or first-run migrations. Check task health again before you retry.Service URLs and domains
Each project has a managed URL on the apps.springwinter.dev domain. This URL stays available when you add a custom hostname. You can add a custom hostname in project settings. Spring Winter creates and attaches a certificate for the custom hostname. Add the DNS and certificate-validation records that Spring Winter shows to your DNS provider. Spring Winter does not change DNS in your account. Both the managed URL and custom hostname route to the service. HTTPS is available for each hostname after its certificate is attached.Choose capacity
The compute settings control CPU, memory, and task copies. More CPU or memory gives each task more resources. More task copies can serve more concurrent requests when your application and its dependencies can use them. These settings do not guarantee a specific request rate. A higher maximum does not enable automatic scaling. Spring Winter shows an estimated monthly cost and its assumptions when you configure the service. The estimate is a guide, not a quote or spending limit. The project Cost page shows billed AWS usage. See Costs and estimates.Change settings
Saved CPU, memory, port, command, volume, and health settings apply on the next redeploy. Runtime environment changes can roll the running service. Build-variable changes apply on the next build. For GitHub sources, the API redeploy action uses the last stored commit by default (source: existing). Use source: branch to resolve the current branch head or source: commit to deploy a specific commit. See the Web Servers API.
When a change requires task replacement, confirm that the new task IDs and intended task definition are serving traffic. Wait for the old tasks to drain before you verify the new behavior or test persistence. A successful workflow can precede completion of the task replacement.
Build and runtime variables
For GitHub sources, expand Build variables in the creation form to configure the first build. Use Runtime variables separately for values the running process needs. Public-image servers have Runtime variables only because Spring Winter does not build their images. After creation, open Environment → Build to edit build values stored in your AWS CodeBuild project. Save build variables does not deploy or restart the service. Select Redeploy, or rebuild the selected preview, to apply them. Declare a matchingARG NAME in the Dockerfile stage that uses each build variable. For example, declare ARG VITE_API_URL before RUN npm run build. Build values can become part of the image or public bundles; use them for configuration, not secrets.
See Environment variables for API scopes, previews, and examples.