mirror of
https://github.com/qdrant/landing_page.git
synced 2026-10-05 10:58:32 +02:00
1a40961d62
* initial commit; fixed anchor links on internal docs pages * add back in absolute paths for links in code comments * fix: update linkchecker include filter to match server port 1314 PR #1629 changed the Hugo server to port 1314 but forgot to update the --include filter, which still matched port 1313. This caused all links to be excluded, making the checker a no-op (0 checked, 82277 excluded). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Fix url rewrite regex so images are not impacted * Fix links from non-documentation pages * Fix broken links * more broken links * more broken links * broken link * Add srcset width descriptor to .lycheeignore * Ignore URLs that contain a % character * Anchor regex so it matches the entire URL --------- Co-authored-by: kanungle <neil.kanungo@gmail.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>
1.9 KiB
1.9 KiB
title, weight, partition
| title | weight | partition |
|---|---|---|
| From S3 Vectors | 35 | ecosystem |
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 configureor 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
| Flag | Required | Description |
|---|---|---|
--s3.bucket |
Yes | S3 bucket name |
--s3.index |
Yes | S3 Vectors index name |
AWS credentials are passed via environment variables or the default AWS credential chain, not CLI flags.
Qdrant-Side Options
| Flag | Default | Description |
|---|---|---|
--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
-eflags or mount your~/.awsdirectory. - Region matters: Ensure the
AWS_REGIONenvironment variable matches the region of your S3 bucket.
Next Steps
After migration, verify your data arrived correctly with the Migration Verification Guide.