# Amazon — Best practices for writing Denied Topics in Amazon Bedrock Guardrails

- Company: Amazon (amazon.com)
- Announced: 2026-11-16T15:48:01+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/best-practices-for-writing-denied-topics-in-amazon-bedrock-guardrails/
- Record: https://forck.live/items/36733-best-practices-for-writing-denied-topics-in-amazon-bedrock-guardrails
- Subject: Bedrock / Nova

Amazon's guide sets out eight best practices for writing Denied Topics in Amazon Bedrock Guardrails, which block a content category by plain-language description applied by meaning rather than keyword. The post says the same mechanism can match more than intended: a topic named Finance, meant to keep an assistant out of investment advice, also blocks "When does my direct deposit clear?". It attributes over- and under-blocking to four authoring patterns: topics framed around a subject domain, definitions built from keyword lists, examples that teach the wrong thing, and overlapping topics that interfere with each other. The practices are worked through on a fictional AnyCompany Bank assistant that answers account, transfer, card and mortgage questions and must refuse personalized investment recommendations, litigation guidance, insider-trading advice, weapon-building instructions, prompt-injection attempts and named competitor products. A topic has a name, a definition and up to five examples, and the guardrail evaluates all three together as a single unit. The name can be up to 100 characters, the definition up to 1,000 characters with 100–300 as the practical sweet spot, each example up to 100 characters, and a guardrail can hold up to 30 topics. The post closes with one limitation to plan for regardless of how well the practices are followed: results are not fully deterministic.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/best-practices-for-writing-denied-topics-in-amazon-bedrock-guardrails/:

> With Denied Topics in Amazon Bedrock Guardrails , you block a content category by describing it in plain language, and the guardrail applies that description to every request by meaning rather than by keyword. That same mechanism can also match more than you intend. A topic named Finance, meant to keep an assistant out of investment advice, also blocks “When does my direct deposit clear?”. Inputs close in meaning to the topic can get caught, not only the requests you intended.
> 
> When Denied Topics blocks too much or too little, the cause is usually one of four authoring patterns:
> 
> Topics that block legitimate queries. A topic framed around a subject domain (Finance, Legal, Compensation) rather than the user’s intention can match queries semantically near that domain. This is a frequent failure mode.
> 
> Topics that miss the requests they were written to catch. A definition built from keyword lists (“words like invest, portfolio, stock…”) misses phrasings that use other vocabulary and fires on unrelated inputs that happen to share those words.
> 
> Examples that teach the wrong thing.

---

Record: https://forck.live/items/36733-best-practices-for-writing-denied-topics-in-amazon-bedrock-guardrails
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
