# Amazon Quick custom permissions can deny new AI capabilities by default

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

AWS announced on 19 August 2026 that Amazon Quick custom permissions now include deny by default. Administrators can restrict an AI capability category in a permissions profile so new capabilities are denied at launch for chosen users, roles or the whole account until each one is explicitly allowed.

Amazon Quick custom permissions now include deny by default, a governance setting that restricts new AI capabilities before they reach users, according to an AWS announcement posted 19 August 2026. Previously, new AI capabilities were available to all users on release, so administrators had to react after the fact. The setting is configured in Manage account in Amazon Quick or through the AWS CLI.

An administrator restricts an AI capability category in a custom permissions profile and assigns it to users, roles or the entire account. Quick then denies any new capability in that category at launch, and restricting a category also restricts the capabilities already in it. Administrators explicitly allow each capability when ready. The restriction applies only to the profile you configure, in Regions where Quick is available.

## Related pages

- [AWS Nitro Sandboxes give pods, tasks and agents their own hardware-isolated VM](/news/nitro-sandboxes-eks-ecs-ec2-agents/)
- [Amazon Quick adds smart approvals for actions that agents take](/news/quick-smart-approvals-agentic-actions/)
- [WorkSpaces for AI agents adds OAuth sessions inside existing network boundaries](/news/workspaces-for-ai-agents-oauth-sessions/)
- [All of them](/news/)

## Sources

- https://aws.amazon.com/about-aws/whats-new/2026/08/amazon-quick-deny-by-default/ (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/news/quick-custom-permissions-deny-by-default/
