Skip to content

Qdrant Vector Database

AI Platform & Data Qdrant v1.19.2 Hardened AMI

Qdrant 1.19.2 on Ubuntu 24.04 LTS, set up as a private single-node vector database. It stores embeddings with JSON payloads and returns the nearest matches, with filtering: the retrieval layer behind semantic search, recommendations and RAG applications. HTTP and gRPC listen on the instance itself, every call needs an API key, and your data stays on an EBS volume in your own account. This page covers what is on the image, the defaults it ships with and how billing works.

Get started View on AWS Marketplace
AMI release
0.1.4 (Qdrant v1.19.2)
Recommended
t3.medium
Storage
16 GiB+ encrypted gp3
Access
Session Manager, no inbound ports
Released
Oct 12, 2026
Delivery
Amazon Machine Image in your own AWS account

Vector similarity search with payload filtering

The retrieval layer for RAG and semantic search.

Secure defaults

HTTP and gRPC bind to the loopback interface, and each instance generates its own API key on first boot.

Storage and snapshots persist locally, and the guided walkthrough covers your first collection and search.

Quick start

Full guide →
  1. Subscribe
  2. Launch the instance
  3. Connect
  4. Wait for first boot
  5. Run the walkthrough
  6. Create a collection and search it

What is on the image

  • Qdrant 1.19.2, a Software Sushi build from the upstream release source, installed as /usr/bin/qdrant.
  • A systemd service, qdrant, that starts at boot and runs as the unprivileged qdrant user.
  • First-boot setup that creates this instance's own API key and the configuration file. Nothing secret is baked into the image.
  • A helper client, /opt/sushi/bin/qdrant-api, that makes authenticated REST calls without putting the API key on the command line.
  • A walkthrough script, /opt/sushi/docs/demo.sh, that checks the database end to end.

Cluster mode, the bundled web UI, CORS, snapshot recovery from remote URLs and telemetry are off.

Defaults

Setting Default
HTTP API http://127.0.0.1:6333 (loopback only)
gRPC API 127.0.0.1:6334 (loopback only)
Authentication API key, sent in the api-key header
API key /etc/qdrant/credentials/api.key, root only
Storage /var/lib/qdrant/storage, kept across restarts
Snapshots /var/lib/qdrant/snapshots
TLS Off. Traffic stays on the instance.

The health paths /readyz and /healthz answer without a key. Everything else, including listing and creating collections, needs it.

Ports

Port Protocol Listens on Purpose
6333 HTTP 127.0.0.1 REST API
6334 gRPC 127.0.0.1 gRPC API

No inbound security group rule is needed. You reach the API from your workstation with Session Manager port forwarding.

t3.medium (4 GiB of memory) with an encrypted gp3 root volume of at least 16 GiB and IMDSv2. Choose a larger instance and volume for larger collections. Qdrant itself needs no AWS API permissions.

Billing

You pay an hourly software fee while the instance runs, as shown in the offer terms on the listing, which also shows any free trial. AWS bills EC2, EBS and data transfer separately.

Where to go next

  • Getting started: subscribe, launch, connect and create your first collection.
  • Configuration: files, the API key, client access and what the first-boot check enforces.
  • Operations: security model, service management, backups, updates and support.
  • Troubleshooting: common errors and how to fix them.

Upstream project

Qdrant is developed by Qdrant Solutions GmbH and published under the Apache-2.0 license. See the Qdrant documentation for collections, search, filtering and client libraries. Software Sushi packages the image; Qdrant Solutions GmbH does not endorse it, and its support is not included.

Last updated October 13, 2026 · Suggest an improvement