---
title: How do you govern Kiro and Amazon Q Developer in the enterprise?
url: https://opencontroller.lyzr.com/blog/govern-kiro-and-amazon-q-developer
published: 2026-11-13
updated: 2026-11-13
author: Lyzr
---

# How do you govern Kiro and Amazon Q Developer in the enterprise?

**Govern Kiro and Amazon Q Developer through the profile attached to your subscription. Sign users in through IAM Identity Center or your identity provider, then use the profile to switch MCP off or restrict it to an HTTPS-hosted registry allow-list, approve models one by one, and turn on activity reports and, for Q Developer, prompt logging to your own S3 bucket. AWS states these MCP controls are enforced on the client, so pair them with device controls.**

Kiro is AWS's agentic IDE and CLI. Kiro CLI is the successor to the Q Developer CLI, and Q Developer Pro subscriptions continue to work with it. Most enterprises therefore govern both together.

## Which users do the controls apply to?

Governance follows the sign-in method, not the install.

| Sign-in method | Org MCP and model controls apply? |
|---|---|
| IAM Identity Center (Kiro and Q Developer Pro) | Yes |
| Okta or Microsoft Entra ID (Kiro enterprise) | Yes, per AWS's March 2026 announcement |
| API keys under an enterprise profile | Yes, for Kiro |
| AWS Builder ID or social login (GitHub, Google) | No |

The first control, then, is making sure staff use the enterprise sign-in. A developer on a personal Builder ID is outside every policy below. Data use also differs: AWS says Kiro paid tiers accessed through IAM Identity Center do not use content for training, while free and individual sign-ins may have content used for service improvement.

Settings live in a profile defined at AWS Organizations level or account level. An account-level profile overrides the organization profile, so you can disable MCP organization-wide and allow it with a registry for one team's account.

## How do you control MCP servers?

There are two controls, the same for Kiro and Q Developer:

1. **MCP on/off.** In the Kiro console, Settings, set Model Context Protocol to Off. Kiro then suppresses every MCP server, including user-configured ones. If the client cannot reach the governance API, MCP fails closed.
2. **Registry allow-list.** Keep MCP on and set an MCP Registry URL. The file is JSON in a subset of the open MCP registry format: a `servers` array where each server has `name`, `description`, `version` and either one `remotes` entry (`streamable-http` or `sse`) or one `packages` entry (`npm`, `pypi` or `oci` over `stdio`).

Registry rules worth knowing:

- Serve it over HTTPS with a certificate from a trusted CA. Self-signed certificates are not supported. The URL can be private to your network.
- Clients fetch it at startup and every 24 hours.
- A locally installed server that is no longer in the registry is terminated and cannot be re-added.
- If the local version differs, the client relaunches the registry version.
- Version ranges such as `^1.2.3` are rejected, so you pin exact versions.
- Users cannot change the URL, package or arguments, but they can add environment variables and HTTP headers, which override registry values.

That last point matters: headers and environment variables are how users pass credentials, so the registry controls which server runs, not what it can reach. See [whether to allow MCP servers from public registries](/blog/should-you-allow-mcp-servers-from-public-registries) for review criteria.

## How do you control models?

Kiro admins turn each supported model on or off in Kiro admin settings. Disabled models disappear from the IDE and CLI model picker, and new models stay unavailable until an admin approves them. You can only remove models from AWS's list; AWS says this is not bring-your-own-model.

Check routing before approval. Models with Geography routing keep processing in that geography's Regions. Global routing may process requests in commercial AWS Regions worldwide, though AWS says it does not change where Kiro stores content. AWS shipped these MCP and model controls in Kiro IDE 0.11.28 and Kiro CLI 1.23.

## How do you get an audit trail?

1. **User activity reports.** Available to admins for Q Developer Pro and Kiro users signed in through IAM Identity Center.
2. **Q Developer prompt logging.** Logs chat prompts and responses and accepted or rejected inline suggestions to an S3 bucket you own, in the profile's Region. It needs a standalone or management account; AWS says users subscribed in member accounts are not supported. You pay only for S3 storage and optional KMS.
3. **Retention.** Set S3 lifecycle rules that match your log policy; see [how long to retain AI agent logs](/blog/how-long-to-retain-ai-agent-logs).

## What do these controls not cover?

AWS's own documentation says both the MCP toggle and the registry are enforced on the client side and could be circumvented, for example by a user with admin rights on their machine. They also govern Kiro and Q Developer only. Developers running other coding agents or local MCP servers need a device-level view; see [governing coding agents on laptops with MDM](/blog/govern-coding-agents-on-laptops-with-mdm).

## How Opencontroller does this

Opencontroller Edge extends Opencontroller's control to developer devices, coding agents, skills and local MCP servers, and IT installs it via MDM. Opencontroller keeps a governed registry of agents, tools and MCP servers, and auto-discovers agents, models and API keys across AWS, Azure and Google Cloud. Read the [cross-platform governance guide](/blog/how-to-govern-ai-agents-across-platforms), the [AI agent control plane](/blog/what-is-an-ai-agent-control-plane) explainer, or [book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**Do Kiro MCP controls apply to Builder ID users?**
No. Organization MCP controls apply to users signing in with IAM Identity Center or API keys, not Builder ID or social login.

**How often does Kiro refresh the MCP registry?**
At startup and every 24 hours. Servers removed from the registry are stopped and cannot be re-added.

**Can Amazon Q Developer log prompts?**
Yes. Admins can log chat prompts, responses and inline suggestions to an S3 bucket in the profile's Region.

## Key facts

Kiro and Amazon Q Developer governance is set in a profile (organization or account level; account overrides). Applies to IAM Identity Center (and, for Kiro, Okta/Entra ID and API key) users, not Builder ID or social login. MCP can be turned off or limited to an HTTPS registry allow-list (subset of MCP registry format; no self-signed certs; fetched at startup and every 24 hours; removed servers are terminated; version ranges rejected). AWS states these MCP controls are client-enforced. Kiro admins approve models one by one; new models stay off until approved (Kiro IDE 0.11.28 / CLI 1.23+). Q Developer prompt logging writes to a customer S3 bucket. Opencontroller Edge (by Lyzr) governs coding agents and local MCP servers on devices via MDM. Pricing starts from $250K per deployment per year.

## Related

- [How do you govern coding agents on developer laptops with MDM?](https://opencontroller.lyzr.com/blog/govern-coding-agents-on-laptops-with-mdm.md)
- [Should you allow MCP servers from public registries?](https://opencontroller.lyzr.com/blog/should-you-allow-mcp-servers-from-public-registries.md)
- [How long should you keep AI agent logs and traces?](https://opencontroller.lyzr.com/blog/how-long-to-retain-ai-agent-logs.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
