# AWS announces S3 Vectors metadata pre-filtering for GovCloud > AWS announces metadata pre-filtering in both GovCloud regions, with defaults for indexes in new vector buckets and an in-place upgrade for existing indexes. Canonical URL: https://www.devobs.io/news/news-event-030f564a844e2ac582e2ea43/ By: Lena Fischer Published: 2026-10-10T05:34:54.787Z Updated: 2026-10-10T05:34:54.787Z Event date: 2026-10-09 Section: Cloud ## Filtering before similarity search AWS announced on October 9, 2026, that Amazon S3 Vectors metadata pre-filtering is available in AWS GovCloud (US-East) and AWS GovCloud (US-West), while noting that deployment was still underway. The feature evaluates metadata conditions before similarity search. AWS says it can return **up to five times more matching vectors** when a filter is selective. That is a result-count claim, not a query-speed benchmark. [AWS announcement](https://aws.amazon.com/about-aws/whats-new/2026/10/s3-vectors-metadata-pre-filtering-in-govcloud-regions/) The release also adds the `$startsWith` prefix-match operator for filtering metadata values such as paths and URLs. For retrieval-augmented generation and semantic-search systems, the engineering question is whether these changes return more useful candidates under the application's actual metadata constraints. [Feature details](https://aws.amazon.com/about-aws/whats-new/2026/10/s3-vectors-metadata-pre-filtering-in-govcloud-regions/) ## New-bucket defaults and existing-index migration AWS says indexes in **new vector buckets** in GovCloud use pre-filtering by default, without changes to how applications write vectors with `PutVectors` or submit filtered searches with `QueryVectors`. Existing indexes have a separate adoption path: an in-place update through `UpdateIndexMode`. Before updating, teams can compare pre-filtering with their current filtering on the same index using a per-query `QueryVectors` parameter. [Migration details](https://aws.amazon.com/about-aws/whats-new/2026/10/s3-vectors-metadata-pre-filtering-in-govcloud-regions/) That comparison is the useful engineering checkpoint. Teams should test representative filters with different selectivity levels, checking result counts, relevance and latency rather than assuming the headline improvement applies uniformly. For RAG workloads, evaluate downstream answer quality separately; candidate count alone does not establish it. ## Announced availability, with deployment still underway The October 9 notice names both GovCloud regions but also says deployment is in progress and expected to finish “in the coming days.” It therefore does not establish that rollout was complete everywhere on announcement day. The same notice separately lists availability in all commercial AWS regions supporting S3 Vectors and in AWS China regions. [Regional availability notice](https://aws.amazon.com/about-aws/whats-new/2026/10/s3-vectors-metadata-pre-filtering-in-govcloud-regions/) ## Source references -