Writing denied topics in Amazon Bedrock Guardrails
What happened
On 16 November 2026, the AWS Machine Learning Blog published an article on best practices for writing Denied Topics in Amazon Bedrock Guardrails. The article notes that Denied Topics match by meaning rather than keywords, so they can easily catch legitimate requests with similar meanings. Using a fictional AnyCompany Bank customer service assistant as an example, it describes a common failure mode: defining topics by subject area (such as Finance or Legal) rather than by user intent. The article then sets out eight writing practices. This is currently the only report on the matter, with no further developments.
Written by AI from the reports · updated 10 h ago
Timeline
Follow the reports to see the event from each side.
- AWS Machine Learning BlogBest 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 matches by meaning rather than keyword, which can block more than you intend. This post presents eight best practices for writing a topic precisely enough that the guardrail blocks what you mean and passes what you don't.
Heat of this event
Current heat 7·Peak in the comparable range 10(Nov 17 01:00)·Change over 24 hours in the comparable range –
The trend compares only the same accounts observed without a break, so its range can be narrower than the current heat count. Move the pointer or tap the chart to see each hour; with a keyboard, use the left and right arrow keys.