General changelog

Loading image...

Enterprise administrators can now share Kiro credits across seated users with credit pooling. In the Kiro console, the feature is labeled Credit sharing. Each seat costs $20 per month and adds 500 monthly credits to one shared pool, so credits one user doesn't use stay available to the rest of the team. Seat price and credits are prorated for the first month.

Admins can add users or groups, set per-user, per-group, and per-profile usage limits, monitor pool usage, and buy additional credits that are good for one year from purchase. Credit pooling is the only option for new Kiro profiles. Existing customers can move users from individual subscriptions with the Switch to credit sharing wizard. You can't undo the switch. Learn more ->

Kiro is now in scope for FedRAMP Class C in the US East (N. Virginia) Region. US government agencies, contractors, and other organizations whose workloads are subject to FedRAMP Class C requirements can now use Kiro for AI-assisted software development.

FedRAMP is a US government-wide program that delivers a standard approach to security assessment, certification, and continuous monitoring for cloud products and services. See AWS services in scope by compliance program for current Kiro scope details, AWS compliance resources for program details, and FedRAMP on AWS for background on the FedRAMP program itself.

Kiro is included in the defined scope of AWS's ISO/IEC 27001:2022 certification. This gives security, procurement, and vendor-risk teams independently verified evidence they can use when evaluating Kiro.

ISO/IEC 27001 sets requirements for an information security management system: the policies, processes, responsibilities, and controls an organization uses to identify and manage information security risks. AWS's certification is verified by EY CertifyPoint, an ISO certification body accredited by the Dutch Accreditation Council.

Organizations can consider this evidence alongside their own policies, intended use, data requirements, and governance controls.

For details about Kiro's compliance programs and access to available third-party reports, see Compliance validation. To learn how Kiro stores, processes, and protects customer data, see Data protection.

Account administrators can now send per-user Kiro usage metrics to their OpenTelemetry-compatible observability platform. Monitor adoption, engagement, and credit consumption by user and model without configuring individual developer environments. Use OTLP alongside the existing daily CSV report to integrate Kiro metrics directly into dashboards and monitoring workflows.

Connect Amazon CloudWatch, Datadog, Elastic, Honeycomb, OpenSearch through an OTLP receiver, or your own collector using OTLP/gRPC or HTTP/protobuf. Set up one account-level export in the Kiro console with an AWS Secrets Manager secret and a publicly reachable OTLP endpoint. Kiro delivers metrics server-side every day at 02:00 UTC. Learn more ->

Kiro Enterprise administrators in AWS GovCloud (US) can now monitor organizational usage through the Kiro console. The usage dashboard provides aggregate metrics; daily per-user activity reports deliver credits, model usage, and other telemetry as CSV files to an Amazon S3 bucket in your account. Administrators can also enable prompt logging to capture user prompts and Kiro responses for compliance and debugging. Kiro does not charge for these monitoring features beyond the associated Amazon S3 storage costs. Learn more ->

Enterprise administrators can now set custom caps for overages using AWS Service Quotas. The quota field Maximum allowed overage per Kiro profile controls the maximum allowed overage for every user in the profile, preventing unexpected costs while keeping users productive. Admins can manage overage caps directly in the Service Quotas console, or navigate there from the Manage link in the Overages setting in the Kiro console. Learn more ->

Loading image...

Individual users on paid plans (Pro, Pro+, Pro Max, and Power) can now purchase add-on credits to continue working after exhausting their monthly allocation. Add-on credits replace the previous overage model with a prepaid approach that gives you full control over spending.

Here's how it works:

• $0.04 per credit, billed immediately when you buy a pack
• Pack sizes range from $5 (125 credits) to $100 per pack
• Up to 5 packs at a time - earliest-expiring pack is consumed first
• 12-month expiry - unused credits roll over month to month until used or expired
• Plan credits first - Kiro uses your monthly allocation before touching add-on credits

Purchase from the Kiro portal via the Buy add-on credits button. Learn more ->

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). Federal agencies, public sector organizations, and enterprises with these compliance requirements can use the Kiro IDE and CLI for sensitive development workloads within AWS GovCloud (US).

Model availability in Kiro does not by itself indicate that a specific model carries FedRAMP High or DoD IL-4/5 authorization. Only models explicitly listed within the Amazon Bedrock service scope carry those authorizations. Learn more ->

Kiro Pro Max is a new $100/month tier that fills the gap between Pro+ ($40/month) and Power ($200/month) — for developers who consistently use more than their Pro+ allocation but don't need everything in Power. You get 5,000 credits per month (2.5x Pro+), all premium models, and the full feature set including specs, custom subagents, powers, and hooks. Switch to Pro Max from your account settings, mid-cycle charges are prorated and your new credit allocation takes effect immediately. Try it now ->

The daily user activity report now includes a User_Email column containing each user's email address. Enterprise admins no longer need to cross-reference user IDs with a separate directory to identify who generated specific activity. The email appears alongside existing fields like UserId, Subscription_Tier, and Total_Messages in the CSV delivered to your S3 bucket. Learn more ->