ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial3 min readDisconfirmAI Editorial

Amazon Web Services: Retrieval Instructions Control How Answers Are Written, Metadata Filters Control What Is Retrieved—A Multi-Tenant Customization Approach for Shared Knowledge Bases

The Amazon Web Services Machine Learning Blog introduces the retrieval instruction feature of Amazon Bedrock Managed Knowledge Base. The core distinction is that instructions set each tenant's voice, format, retrieval guidance, and answer policy, while metadata filters control which documents each tenant can retrieve; the two operate independently. The article also notes that answer policies are best-effort—if restricted documents are retrieved, answers may still reference their mechanisms or record IDs, so data isolation must rely on filters rather than policy text.

2026-11-16 23:46 GMT+8

The same product documentation and policy files often serve different audiences: customers in three sales regions need their own languages and date formats, while internal support teams need short ticket notes. Previously, implementing this differentiation on Amazon Bedrock Managed Knowledge Base required developers to disable response generation, call models themselves, and maintain prompts in every application. An article published by the Amazon Web Services Machine Learning Blog in November 2026 introduced a new mechanism: retrieval instructions—a versioned managed resource referenced by each request, eliminating the need to duplicate maintenance across applications.

The article's core distinction is noteworthy: retrieval instructions change how answers are written but do not limit what is retrieved. Instructions have four fields—persona sets identity, tone, and language; answerFormat specifies structure, date and currency formats, and citation style; retrievalGuidance directs the agent on how to interpret questions and prioritize document searches; answerPolicy determines whether to answer and how to handle out-of-scope questions. Among these, persona, answerFormat, and answerPolicy only take effect when generateResponse is true, while retrievalGuidance applies regardless of response generation. However, the author explicitly warns that these fields are not authorization or data-isolation boundaries. To ensure different tenants see only their own documents, metadata filters or separate knowledge bases must be used to control the retrieval scope.

Sign in / Sign up
ReadingResearchRadarInvestment framework

This distinction has an easily overlooked consequence in practice: answer policies are best-effort. The article gives an example where, even if the instruction states that restricted engineering notes should never be discussed, if the agent retrieves those notes, the answer might still mention their mechanisms or record IDs. To truly exclude restricted content from answers, one should use metadata filters to exclude documents containing that content from the retrieval scope. In other words, the instruction layer handles style control, while the filter layer constitutes the security boundary—confusing the two leads to situations where data appears protected by policy but has actually leaked.

Regarding version management, the article recommends pinning specific versions in production environments rather than using DRAFT. After updating an instruction, one must poll to wait for asynchronous review completion; creating a version or updating again during the review returns HTTP 409. When publishing changes, the application layer maintains version mappings for each tenant, enabling canary releases, promotions, or rollbacks by modifying the mapping—Amazon Bedrock itself does not route traffic. A single request can reference only one retrieval instruction, so users belonging to both a region and a team require a combined instruction covering both, or must accept a compromise of using the team instruction plus a regional tenant line. The default quota is 50 retrieval instructions per account per region.

The article also demonstrates broader usage: answerFormat can demand strict JSON output for downstream code consumption, saving a separate generation step; retrievalGuidance can teach the agent domain vocabulary and preferred sources; answerPolicy can fix disclaimers and citation formats. These usages are not limited to multi-tenant scenarios, though multi-tenancy serves as the article's primary narrative framework.

Sources

  • aws.amazon.comAmazon Web Services↗
Continue researching →