Skip to main content

Deploy with an agent

Copy agent prompt

Before you start

Connect your AWS account and choose a project. Review the upstream deployment instructions for the release you plan to pin.

Data dependencies

Qdrant is the database. You do not need PostgreSQL or MySQL.

Deployment order

  1. Choose Qdrant Cloud or a persistent container host with supported block storage and a POSIX filesystem. Attach durable storage at /qdrant/storage before starting a self-hosted instance.
  2. Configure TLS and an API key. Use the private HTTP endpoint on port 6333 for REST or port 6334 for gRPC when your network supports it. Keep intra-cluster ports private if using a cluster.
  3. Store the endpoint and scoped API key in the Spring Winter client application’s runtime configuration. Qdrant REST clients authenticate with the api-key header.
  4. Start and verify Qdrant first. Create or initialize collections, then deploy the Spring Winter application that indexes and queries them.
Use Runtime variables for runtime credentials. For a Spring Winter web server, set an app-supported health path that returns HTTP 200 without credentials. Check History before running the application check.

Verify the deployment

Index a few sample vectors, query them with a read-only key, and verify the collection persists after a restart.