--- title: Amazon Quick adds deny by default for custom permissions description: Amazon Quick now supports deny by default for custom permissions, letting administrators block new AI capabilities from reaching users automatically instead of... canonical: https://daily.dev/posts/amazon-quick-adds-deny-by-default-for-custom-permissions-ktu7xd04k twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Amazon Quick adds deny by default for custom permissions | daily.dev og:description: Amazon Quick now supports deny by default for custom permissions, letting administrators block new AI capabilities from reaching users automatically instead of... og:url: https://daily.dev/posts/amazon-quick-adds-deny-by-default-for-custom-permissions-ktu7xd04k og:image: https://api.daily.dev/og/posts/Ktu7XD04k.png og:image:alt: Amazon Quick adds deny by default for custom permissions og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Amazon Quick adds deny by default for custom permissions **[AWS](https://daily.dev/sources/aws)** · 1 min read · 0 upvotes · 0 comments ## Summary Amazon Quick now supports deny by default for custom permissions, letting administrators block new AI capabilities from reaching users automatically instead of reacting after release. Admins can restrict an AI capability category in a custom permissions profile and apply it to users, roles, or the whole account; restricting a category also blocks existing capabilities within it, and each capability must be explicitly allowed when ready. The setting is configured through Manage account in Amazon Quick or the AWS CLI and is available in all regions where Amazon Quick operates. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is deny by default in Amazon Quick custom permissions? Deny by default is a governance setting in Amazon Quick that automatically restricts new AI capabilities from reaching users until an administrator explicitly allows them. Previously, new AI capabilities were available to all users immediately upon release, requiring admins to react after the fact. Restricting a category also blocks existing capabilities within it, and admins configure it via Manage account or the AWS CLI. _Admins standardizing AI permission governance can track AWS updates like this through daily.dev._ ### How do I configure deny by default for AI capabilities in Amazon Quick? Administrators configure deny by default through Manage account in Amazon Quick or via the AWS CLI, restricting an AI capability category in a custom permissions profile and assigning it to specific users, roles, or the entire account. Any new AI capability launched afterward is automatically denied for that profile until explicitly allowed, and the restriction applies only to the configured profile. _Teams rolling out AWS AI features can follow governance changes like this via daily.dev._ ## Similar posts on daily.dev - [Amazon Quick now supports per-user resource limits](https://daily.dev/posts/amazon-quick-now-supports-per-user-resource-limits-vtiqooanl) · AWS · 0 upvotes · 0 comments - [Amazon Quick now supports approval policies for sharing](https://daily.dev/posts/amazon-quick-now-supports-approval-policies-for-sharing-pdfrkfost) · AWS · 0 upvotes · 0 comments - [Amazon Quick now lets you build custom apps with natural language](https://daily.dev/posts/amazon-quick-now-lets-you-build-custom-apps-with-natural-language-3fdfpmjd1) · AWS · 0 upvotes · 0 comments - [Managing AI Costs: Step-by-Step Tutorial to Set Up a Per-User Quota to Control Your AI Spend](https://daily.dev/posts/managing-ai-costs-step-by-step-tutorial-to-set-up-a-per-user-quota-to-control-your-ai-spend-dwijgcqrl) · Snowflake Community · 0 upvotes · 0 comments --- Tags: [#security](https://daily.dev/tags/security), [#aws](https://daily.dev/tags/aws) [View this post on daily.dev](https://daily.dev/posts/amazon-quick-adds-deny-by-default-for-custom-permissions-ktu7xd04k) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Amazon Quick adds deny by default for custom permissions","url":"https://daily.dev/posts/amazon-quick-adds-deny-by-default-for-custom-permissions-ktu7xd04k","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/amazon-quick-adds-deny-by-default-for-custom-permissions-ktu7xd04k"},"datePublished":"2026-08-17T15:04:10.749Z","dateModified":"2026-09-13T18:31:52.651Z","description":"Amazon Quick now supports deny by default for custom permissions, letting administrators block new AI capabilities from reaching users automatically instead of...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e82c8cceed8771f89f06dfc50fa9305d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e82c8cceed8771f89f06dfc50fa9305d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"AWS","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"AWS","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/aws","url":"https://daily.dev/sources/aws"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/amazon-quick-adds-deny-by-default-for-custom-permissions-ktu7xd04k","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,aws","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"AWS","item":"https://daily.dev/sources/aws"},{"@type":"ListItem","position":3,"name":"Amazon Quick adds deny by default for custom permissions"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/amazon-quick-adds-deny-by-default-for-custom-permissions-ktu7xd04k#faq","mainEntity":[{"@type":"Question","name":"What is deny by default in Amazon Quick custom permissions?","acceptedAnswer":{"@type":"Answer","text":"Deny by default is a governance setting in Amazon Quick that automatically restricts new AI capabilities from reaching users until an administrator explicitly allows them. Previously, new AI capabilities were available to all users immediately upon release, requiring admins to react after the fact. Restricting a category also blocks existing capabilities within it, and admins configure it via Manage account or the AWS CLI. Admins standardizing AI permission governance can track AWS updates like this through daily.dev."}},{"@type":"Question","name":"How do I configure deny by default for AI capabilities in Amazon Quick?","acceptedAnswer":{"@type":"Answer","text":"Administrators configure deny by default through Manage account in Amazon Quick or via the AWS CLI, restricting an AI capability category in a custom permissions profile and assigning it to specific users, roles, or the entire account. Any new AI capability launched afterward is automatically denied for that profile until explicitly allowed, and the restriction applies only to the configured profile. Teams rolling out AWS AI features can follow governance changes like this via daily.dev."}}]} ```