Skip to content
Qdrant Vector Database for AI product logo
  • AWSAvailable on Amazon Web Services
  • Azure· soonComing soon on Microsoft Azure
  • GCP· nextGoogle Cloud is next on the roadmap
Available

Qdrant Vector Database for AI

A ready-to-use vector search and AI workbench: Qdrant 1.19.1 with JupyterLab, MinIO object storage and a CPU PyTorch environment with sentence-transformers. Embed, index and search on the instance the moment it boots - no API keys, no external services - with a quickstart notebook that runs clean out of the box.

Version
v1.19.1
Operating system
Ubuntu 24.04 LTS
Architecture
x86_64
Support
Email support

What's installed

Every package and version on the image, identical on every cloud it ships on. Nothing else is installed.

  • Qdrant 1.19.1
  • JupyterLab 4.6.3
  • MinIO RELEASE.2025-09-07
  • PyTorch 2.14.0 (CPU)
  • sentence-transformers 6.0.1
  • qdrant-client 1.19.0
  • nginx 1.24.0

LicensingOpen source (Qdrant Apache-2.0, MinIO AGPL-3.0), no licence key required

Deploy anywhere

Qdrant Vector Database for AI on AWS and Azure.

Google Cloud is next on the roadmap. One clean-room build, one first-boot credential model, one patch cadence — identical on every cloud you run. Every identifier below is the real one; copy it and launch.

  1. AWS
    Available

    Amazon Web Services

    AMI · v1.19.1

    AWS AMI ID

    Shown for your region on the AWS Marketplace launch page once you subscribe.

    Released
    Root volume
    gp3 · 30 GiB
    Instance types
    • t3a.large
    • t3.large
    • t3a.xlarge
    • m6a.xlarge
    Regions34 regions· show all
    • us-east-1
    • af-south-1
    • ap-east-1
    • ap-east-2
    • ap-northeast-1
    • ap-northeast-2
    • ap-northeast-3
    • ap-south-1
    • ap-south-2
    • ap-southeast-1
    • ap-southeast-2
    • ap-southeast-3
    • ap-southeast-4
    • ap-southeast-5
    • ap-southeast-6
    • ap-southeast-7
    • ca-central-1
    • ca-west-1
    • eu-central-1
    • eu-central-2
    • eu-north-1
    • eu-south-1
    • eu-south-2
    • eu-west-1
    • eu-west-2
    • eu-west-3
    • il-central-1
    • me-central-1
    • me-south-1
    • mx-central-1
    • sa-east-1
    • us-east-2
    • us-west-1
    • us-west-2
    Launch on AWS MarketplaceAWS launch steps

    5-day free trial, then from $0.04/hr software charge (larger instance sizes cost more) plus your own EC2 costs, billed by AWS.

    Subscriptions are open to AWS India (AISPL) accounts. Outside India? Ask us for a private build.

  2. Azure
    Coming soon

    Microsoft Azure

    Compute Gallery image · v1.19.1

    Azure Compute Gallery image ID
    …/galleries/provencloud/images/qdrant/versions/2026.9.1
    Released
    OS disk
    Premium_LRS · 30 GiB
    Gallery
    provencloud
    Definition
    qdrant
    Resource group
    provencloud-images-rg
    VM sizes
    • Standard_D2as_v7
    • Standard_D4as_v7
    • Standard_D8as_v7
    • Standard_D2as_v5
    Regions
    • eastus
    Azure launch steps
AWS

Getting started on Amazon Web Services

From launch to signed in, step by step.

  1. Subscribe on AWS Marketplace and launch in your region with TCP 22, 80, 8888 and 9001 open (and 9000 if you will use the S3 API from outside); wait two to three minutes.

  2. Open http://<instance-public-ip>/ for the stack home page with a live status light per service. Qdrant dashboard: /dashboard. REST API at the root, no authentication.

  3. JupyterLab: http://<instance-public-ip>:8888, password = your EC2 Instance ID (for example i-0123456789abcdef0). MinIO console: port 9001, admin / minioadmin123.

  4. Change the MinIO credential before storing real data - it is published and identical on every copy of this image: sudo bash /home/ubuntu/iscripts/pass_minio.sh.

  5. The quickstart notebook 01-quickstart.ipynb opens automatically. From your own code, point any Qdrant client at http://<instance-public-ip> (or localhost:6333 on the instance).

  6. The Qdrant API has no authentication: restrict port 80 to the addresses that need it. qdrant-status reports the whole stack.

Security posture

What this AWS image does and does not ship with, one fact per line.

  • Clean-room build on Canonical's official Ubuntu 24.04 LTS image: every component comes from its own official repository or release, nothing is copied from any third-party image, and the finished image was scanned for third-party vendor strings before capture.

  • No usable credential ships in the image; passwords are set on your instance at first boot from EC2 instance metadata (IMDSv2) and the scripts that set them delete themselves afterwards.

  • SSH is key-only, root login over SSH is refused, and build-time SSH keys, shell history and logs were removed before imaging.

  • Two things to act on before real data: the Qdrant API on port 80 has no authentication, so restrict that port to the addresses that need it or put your own auth in front, and the MinIO root credential is a documented default that pass_minio.sh replaces in one step (it rolls back automatically if MinIO fails to restart).

  • JupyterLab is already unique to your instance, its password set from the Instance ID at first boot.

  • Qdrant's own ports (6333/6334) are bound to 127.0.0.1 and published only through nginx.

  • Qdrant and MinIO run as dedicated nologin accounts under hardened systemd units and restart on failure; checksums were verified for every release binary.

  • The bundled password tools enforce at least 10 characters with upper- and lower-case letters, a number and a symbol, and verify the new credential with a real sign-in before reporting success.

  • The image is HTTP-only by design so it works at a bare IP with no certificate warnings: terminate TLS at a load balancer or add a certificate before exposing it publicly, and restrict port 22 and any admin ports to trusted IP ranges in your security group.

Azure

Getting started on Microsoft Azure

From launch to signed in, step by step.

  1. Deploy the gallery image in eastus with TCP 22, 80, 8888 and 9001 open in your network security group. Choose ubuntu as the administrator username so SSH and the script paths match. Wait about three minutes for first boot.

  2. Open http://<vm-public-ip>/ for live status, and /dashboard for the Qdrant dashboard. JupyterLab is on port 8888 (password only, no username) and the MinIO console on port 9001 (username admin).

  3. The password is your VM ID: in the Azure portal open the virtual machine, choose Properties and copy VM ID - a 36-character value such as 02aab8a4-74ef-476e-8182-f6d2ba4166a6, typed exactly as shown in lower case.

  4. SSH as ubuntu with your key. Qdrant itself listens on 127.0.0.1:6333 - reach it from your own code on the VM, or put your own authenticated proxy in front of it.

Security posture

What this Azure image does and does not ship with, one fact per line.

  • Clean-room build on Canonical's official Ubuntu image from the Azure Marketplace: every component comes from its own official source and no third-party image was launched or copied.

  • Both the JupyterLab password and the MinIO console password are set on first boot from your VM's own vmId - no fixed default survives capture.

  • Qdrant is bound to 127.0.0.1 and reached only through nginx.

  • The pre-image cleanup proves the build's own credentials are rejected before capture, and first boot sets every password from the new VM's own vmId, read from Azure IMDS.

  • The ubuntu login account ships password-locked with an empty authorized_keys, and cloud-init installs your own SSH key at deploy time.

  • Shell history, logs and cloud-init state are cleared before capture.

  • Verified against Microsoft's documented Linux certification test cases on a VM deployed from this gallery version - 13 passed, 0 failures - with VM extension provisioning confirmed and every helper script executed rather than only reviewed.

  • Restrict port 22 to trusted IP ranges, and put the consoles behind HTTPS with your own certificate before exposing them to the internet.