AWS Quick is adding configurable guardrails that let administrators test or block prompts containing sensitive information and other restricted content. The preview gives enterprise teams a way to try policies against live traffic before switching enforcement on, rather than making the first test a user-facing surprise.
AWS AI Watch analysis
What happened
AWS says administrators can create policies using content filters, denied topics, blocked words and phrases, prompt-attack detection, and controls for selected types of personally identifiable information. A policy can be assigned to an individual, an identity-provider group, or set as the account default.
When policies overlap, user-level policies take precedence over group policies and account defaults. Multiple group policies combine their restrictions, with the stricter setting applying where controls overlap. In detect-only mode, Quick evaluates prompts and logs policy matches without blocking requests. Once enforcement is enabled, matching prompts are blocked and users see a message; administrators can review detected and blocked events in Amazon CloudWatch Logs.
The feature is in preview for select Quick customers on Professional and Enterprise plans, according to AWS.
Why it matters
These controls give organisations a practical route to test how prompt restrictions affect everyday work before imposing them. They can, for example, check whether blocking confidential project names catches the intended prompts without disrupting legitimate business tasks.
That is useful governance plumbing, but it is not a guarantee that a policy will catch every sensitive prompt or prompt attack. The detect-only stage helps teams examine the rules’ effects; the actual policy choices still belong to administrators.
Our read
The preview’s strongest feature is the chance to test policies before they start blocking people. That is a more sensible opening move than discovering a rule is too broad when an employee is trying to get work done. Enterprise teams should treat the trial as a chance to tune policies against real workflows, not as proof that a guardrail makes data handling safe by itself.
What to watch
- Whether AWS expands preview access or announces general availability.
- How administrators can inspect and refine detected policy matches.
- Which regions and Quick customers can use the preview.
Discussion spark: Should enterprise AI prompt controls start in detect-only mode by default, or should administrators be able to block risky prompts from day one?
Sources and evidence
- AWS Quick introduces enterprise guardrails (preview) (20 November 2026, 20:30 UTC)
- AWS Quick now supports group assignments for custom permissions and limit profiles (20 November 2026, 20:30 UTC)
- Amazon ECS Action Logs now cover tasks, container instances, and capacity providers (20 November 2026, 20:30 UTC)
- Amazon CloudWatch Observability EKS add-on now supports telemetry filtering (20 November 2026, 20:30 UTC)
not affiliated with or endorsed by Amazon Web Services (AWS)