> ## Documentation Index
> Fetch the complete documentation index at: https://docs.springwinter.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy Kestra

> Set up Kestra and connect its dependencies with Spring Winter.

## Deploy with an agent

Copy agent prompt

Help me deploy Kestra. Read [https://docs.springwinter.dev/deploy/open-source/kestra](https://docs.springwinter.dev/deploy/open-source/kestra.md), [https://kestra.io/docs/installation/docker-compose](https://kestra.io/docs/installation/docker-compose), and [https://docs.springwinter.dev/api-reference/agents](https://docs.springwinter.dev/api-reference/agents.md). Fetch the public OpenAPI specification from my Spring Winter origin. Use my local SPRINGWINTER\_TOKEN or existing SPRINGWINTER\_API\_TOKEN. Keep credentials out of chat, logs and source.

Confirm my project, AWS connection, Region and budget. Pin a release. Check its required services, container port, health path, network access and durable storage. Data requirements for this deployment: PostgreSQL for the repository and queue, plus durable internal storage.

1. Create a private PostgreSQL database and wait for the writer. Create a private S3 bucket before starting Kestra if you use S3 internal storage. Check task credentials permit access to that bucket.
2. Set datasources.postgres.url in KESTRA\_CONFIGURATION to the writer JDBC URL. Set its username and password through runtime configuration. Set kestra.repository.type and kestra.queue.type to postgres. Configure kestra.storage.type and the storage backend.
3. Deploy the pinned Kestra standalone image using the release’s documented command. Configure a task runner compatible with the hosting environment. Use a separate supported execution environment for jobs that require a Docker daemon.
4. Start Kestra after PostgreSQL and storage are ready. Wait for startup before enabling schedules or connecting clients.

Show me the planned resources, database and migration order, secret names and estimated cost. Identify components that require separate hosting. Wait for approval before making changes. Use documented Spring Winter operations and wait for each workflow to finish. Run a simple flow, then verify execution history and read back an output stored by the flow. Report resource links and anything you could not verify.

## Before you start

[Connect your AWS account](https://docs.springwinter.dev/connect-aws.md) and choose a project. Review the [upstream deployment instructions](https://kestra.io/docs/installation/docker-compose) for the release you plan to pin.

See [Kestra runtime and storage configuration](https://kestra.io/docs/configuration/runtime-and-storage).

## Data dependencies

PostgreSQL for the repository and queue, plus durable internal storage. See [SQL databases](https://docs.springwinter.dev/deploy/databases.md) for private writer access and connection details.

## Deployment order

1. Create a private PostgreSQL database and wait for the writer. Create a private S3 bucket before starting Kestra if you use S3 internal storage. Check task credentials permit access to that bucket.
2. Set `datasources.postgres.url` in `KESTRA_CONFIGURATION` to the writer JDBC URL. Set its username and password through runtime configuration. Set `kestra.repository.type` and `kestra.queue.type` to `postgres`. Configure `kestra.storage.type` and the storage backend.
3. Deploy the pinned Kestra standalone image using the release’s documented command. Configure a task runner compatible with the hosting environment. Use a separate supported execution environment for jobs that require a Docker daemon.
4. Start Kestra after PostgreSQL and storage are ready. Wait for startup before enabling schedules or connecting clients.

Use [Runtime variables](https://docs.springwinter.dev/concepts/environment-variables.md) for runtime credentials. For a [Spring Winter web server](https://docs.springwinter.dev/deploy/web-servers.md), set an app-supported health path that returns HTTP 200 without credentials. Check **History** before running the application check.

## Verify the deployment

Run a simple flow, then verify execution history and read back an output stored by the flow.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.