Migrate from S3 Vectors to Qdrant

What You Need from AWS

  • S3 bucket name — the bucket containing your vector data
  • Index name — the S3 Vectors index to migrate
  • AWS credentials — configured via aws configure or environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY)

Run the Migration

docker run --net=host --rm -it \
    -e AWS_ACCESS_KEY_ID='your-access-key' \
    -e AWS_SECRET_ACCESS_KEY='your-secret-key' \
    -e AWS_REGION='us-east-1' \
    registry.cloud.qdrant.io/library/qdrant-migration s3 \
    --s3.bucket 'your-bucket-name' \
    --s3.index 'your-index-name' \
    --qdrant.url 'https://your-instance.cloud.qdrant.io:6334' \
    --qdrant.api-key 'your-qdrant-api-key' \
    --qdrant.collection 'your-collection'

All S3 Vectors-Specific Flags

FlagRequiredDescription
--s3.bucketYesS3 bucket name
--s3.indexYesS3 Vectors index name

AWS credentials are passed via environment variables or the default AWS credential chain, not CLI flags.

Qdrant-Side Options

FlagDefaultDescription
--qdrant.id-field__id__Payload field name for original S3 vector IDs

Gotchas

  • Credential handling: AWS credentials must be available inside the container. Pass them as environment variables with -e flags or mount your ~/.aws directory.
  • Region matters: Ensure the AWS_REGION environment variable matches the region of your S3 bucket.

Next Steps

After migration, verify your data arrived correctly with the Migration Verification Guide.

Was this page useful?

Thank you for your feedback! 🙏

We are sorry to hear that. 😔 You can edit this page on GitHub, or create a GitHub issue.