<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>S3 Vectors on The road</title><link>https://kane.mx/tags/s3-vectors/</link><description>Recent content in S3 Vectors on The road</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 27 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kane.mx/tags/s3-vectors/index.xml" rel="self" type="application/rss+xml"/><item><title>S3 Vectors vs OpenSearch: Decision Tree from 30+ Projects</title><link>https://kane.mx/posts/2026/s3-vectors-vs-opensearch/</link><pubDate>Wed, 27 May 2026 00:00:00 +0000</pubDate><guid>https://kane.mx/posts/2026/s3-vectors-vs-opensearch/</guid><description>
&lt;p>Choosing a vector store on AWS for generative AI (GenAI) workloads used to be a one-line decision: pick Amazon OpenSearch Service or its serverless variant (AOSS) and move on. That changed when &lt;a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-vectors.html">Amazon S3 Vectors&lt;/a> went GA in 2025. By storing vector data directly in S3 and pricing it on a fully consumption-based model, S3 Vectors has reset the cost-performance frontier for vector search.&lt;/p>
&lt;p>This post is not a rehash of the official documentation. It distills selection and tuning experience across more than 30 production GenAI projects shipped over the past year. You will get a decision tree, the cost-crossover math between the two services, and the specific migration pitfalls that bite hardest in practice — including the cosine-distance range mismatch and the metadata structure constraints.&lt;/p>
&lt;p>&lt;a href="https://kane.mx/posts/2026/s3-vectors-vs-opensearch/">Read More&lt;/a>&lt;/p></description></item></channel></rss>