Coding agents / Amazon Web Services
Kiro
Kiro for teams and enterprises (credit pooling seats, sign-in through AWS IAM Identity Center or an external identity provider). Formerly Amazon Q Developer.
$20 per user a month + usage. $20 per seat per month for team credit pooling, with 500 credits per seat; extra credits cost $0.04 each. Official page
MCP serversYes · “MCP servers”
Connects to local and remote MCP servers; admins can govern which servers are allowed.
Model Context Protocol (MCP) extends Kiro's capabilities by connecting to specialized servers that provide additional tools and context.
Models from several companiesYes · “Auto”
Pick OpenAI, Anthropic or open-weight models, or let Auto route each task.
Kiro gives you access to frontier and open weight AI models from OpenAI, Anthropic, and other providers.
Edits across filesYes · “Specs”
Turns a request into a written spec, then plans and makes the change across the codebase.
Instead of reacting to individual prompts, Kiro works from structured specifications to plan, implement, and verify changes across your entire codebase.
Works in the cloudYes · “Kiro Web”
Runs tasks in cloud sandboxes and opens PRs on GitHub or GitLab; an admin must turn on Cloud Sessions.
Connect your GitHub or GitLab repositories or both, describe what you need, and Kiro writes code, coordinates changes across repos, and opens pull requests.
Reviews pull requestsPartly · “Headless mode”
Kiro CLI can run code reviews in a CI pipeline; no built-in bot that posts PR comments is documented.
Headless mode lets you run Kiro CLI as part of your CI/CD pipeline to automate code reviews, generate tests, or troubleshoot build failures
Runs in the terminalYes · “Kiro CLI”
Kiro CLI runs the same agent in the terminal, including headless runs in CI.
Kiro CLI is a tool that allows you to interact with Kiro’s AI agents directly from your terminal.
VS Code and JetBrainsPartly · “ACP”
Works in JetBrains through ACP; for VS Code users Kiro is its own VS Code-based IDE, not an extension.
This means you can use Kiro's agentic capabilities in JetBrains IDEs, Zed, and other ACP-compatible editors.
SSO and SCIMYes · “SCIM provisioning”
SSO through IAM Identity Center, Okta or Entra ID, with SCIM to sync users and groups.
When using Okta, you need to create two applications: one OIDC application for user login, and one SCIM provisioning application
Audit logsYes · “Prompt logs”
Admins can log users' prompts and responses to their own S3 bucket; CloudTrail records Kiro tool calls.
Prompt logs provide you with a record of all the prompts that users enter into Kiro chat in their IDE or the CLI.
Usage reportsYes · “User activity reports”
An admin dashboard plus daily per-user activity reports to S3 or OpenTelemetry.
User activity reports show you what individual users are up to in Kiro.
Data residencyYes · “Kiro profile”
Data stays in the profile's region: US East, Frankfurt or GovCloud. Some models may run in other regions.
your content, such as prompts and responses, may be stored in the region where your profile is configured in order to provide and maintain the service
Not used for trainingYes · “Service improvement”
Enterprise content is not used; free and individual plans may be used unless they opt out.
We do not use content from Kiro enterprise users for service improvement.
SOC 2 and ISO 27001Yes · “ISO/IEC 27001:2022”
Kiro is in AWS's ISO 27001 scope; AWS also lists Kiro in its SOC report scope.
Kiro is included in the defined scope of AWS's ISO/IEC 27001:2022 certification.
HIPAA BAAPartly · “HIPAA eligible”
IDE and CLI are HIPAA eligible, so covered by the AWS BAA; Kiro Web is not listed.
Kiro IDE and CLI are HIPAA eligible.
FedRAMPYes · “FedRAMP High”
IDE and CLI are FedRAMP High in AWS GovCloud (US); each model needs its own authorization.
Kiro is now authorized for FedRAMP High and Department of Defense Cloud Computing Security Requirements Guide Impact Levels 4 and 5 in AWS GovCloud (US).
Copyright protectionYes · “Output indemnity”
Paid subscribers are covered under AWS Service Terms section 50.10; some models are excluded.
Yes, we provide an output indemnity for paid Kiro subscribers.
Public code filterYes · “Reference Tracker”
Code matching public code is off by default; admins can keep it off and users see a reference log.
Administrators can opt out of code references in the Kiro console.
Changes
retiredKiro
Amazon Q Developer IDE plugins and paid plans reach end of support on April 30, 2027
AWS stopped new Q Developer sign-ups on May 15, 2026 and moves customers to Kiro; the IDE plugins and paid subscriptions end on April 30, 2027.
aws.amazon.com