# Amazon Q Business runs on service roles the console creates, and each one is narrow but includes a few wildcard resources

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

Amazon Q Business runs as separate IAM service roles for the application, web experience, data sources and plugins, which the console creates if you let it. AWS documents that the application role writes logs and metrics and the plugin role reads one secret. AWS also states Q Business is closed to new customers. Read 16 Nov 2026.

## Status first: Amazon Q Business is closed to new customers

Each Amazon Q Business page that AWS publishes carries the note that it is no longer open to new customers, and points to Amazon Quick for similar capabilities ([AWS: what is Amazon Q Business](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/what-is.html), read 16 Nov 2026). Existing applications still run, so the roles below matter for accounts that already have one. It is not one of the platforms in [the Agent Access Map](/map/).

## The identity it runs as is a set of service roles, not one role

AWS documents that when you create an application or a web experience, or connect a data source, Q Business needs access to AWS resources, and that you supply an IAM role for each. With the console you can create new roles or pick existing ones, and the console lists roles with qbusiness or QBusiness in the name. If the console creates the roles, AWS documents that the listed policies are created on your behalf ([AWS: IAM roles for Amazon Q Business](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/iam-roles.html)). The topics list six role types: application, web experience, data source connectors, plugins, custom document enrichment and the Amazon Kendra retriever.

Q Business also answers on behalf of end users. AWS documents that its responses are based on the content the end user has permission to access, with access managed through AWS IAM Identity Center or IAM. That is a user-side control layered on top of the service roles.

## What the documented roles let it reach

| Role | Documented permissions | Trust policy |
| --- | --- | --- |
| Application role | cloudwatch:PutMetricData limited to the AWS/QBusiness namespace; logs:DescribeLogGroups on all resources; log group, stream and event writes under /aws/qbusiness/* | Service principal qbusiness.amazonaws.com may call sts:AssumeRole |
| Plugin service access role | secretsmanager:GetSecretValue on the one Secrets Manager secret holding the third-party credentials; optionally the KMS key that encrypts it | Service principal qbusiness.amazonaws.com, with aws:SourceAccount and aws:SourceArn conditions tying it to one application |
| Web experience, data source, enrichment and retriever roles | Listed on their own AWS pages; the data source role depends on the connector | See each page |

## What that lets an attacker or a mistake reach

The application role reaches logging and metrics, not data. The plugin role reaches the credential for the third-party system, such as Jira, Salesforce, ServiceNow or Zendesk, that the plugin was built for. AWS documents that plugins let users perform tasks such as changing the status of a ticket or creating an incident, up to 25 plugins per application ([AWS: configuring actions](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/actions.html)). So the reach into a third-party service is set by the credential in that secret, and a broad credential there is a broad grant. The reach into AWS data comes from the data source roles and the retriever, which depend on what you connect.

Two details to read in the policy text: logs:DescribeLogGroups is allowed on all resources, and the shown plugin trust example substitutes a placeholder for the secret ARN that you must replace with the real one.

## How to narrow it

- Keep one set of roles per application, and add the source account and source ARN conditions to every trust policy; AWS shows them on the plugin role ([check: scope the trust](/checklist/scope-trust-to-the-agent/)).
- Restrict the plugin secret's resource policy and the IAM permissions to read it, and store a third-party credential scoped to the one task the plugin needs ([check: write the policy from the calls](/checklist/least-privilege-policy/)).
- Attach a permissions boundary or an SCP over the Q Business roles so nothing can widen them ([check: set a ceiling](/checklist/set-permission-ceiling/)).
- Review data source roles against the buckets and sites the connector truly indexes, using [the least privilege guide](/guides/least-privilege-for-ai-agents/).
- Read [the AWS cloud page](/clouds/aws/) for the other AWS platforms and their defaults.

## Related pages

- [Copilot Studio default permissions: tool authentication](/default-permissions/copilot-studio/)
- [Azure OpenAI Assistants default permissions and access](/default-permissions/azure-openai-assistants/)
- [Conversational Agents (Dialogflow CX) default permissions](/default-permissions/conversational-agents/)
- [All of them](/guides/)

## Sources

- AWS: what is Amazon Q Business: https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/what-is.html (read 16 Nov 2026)
- AWS: IAM roles for Amazon Q Business: https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/iam-roles.html (read 16 Nov 2026)
- AWS: IAM role for an Amazon Q Business application: https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/create-application-iam-role.html (read 16 Nov 2026)
- AWS: IAM role for Amazon Q Business plugins: https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/plugin-iam-role.html (read 16 Nov 2026)
- AWS: configuring actions in Amazon Q Business: https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/actions.html (read 16 Nov 2026)
- AWS: identity and access management for Amazon Q Business: https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/security-iam.html (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/default-permissions/amazon-q-business/
