
Exploring the Kiro Management Console with CloudTrail Gives a Glimpse of the Underlying Integrated Platform
This page has been translated by machine translation. View original
In February 2026, a user activity report was added as an Enterprise feature of AWS's generative AI coding assistant "Kiro". To make use of this report, I investigated how to retrieve the subscription information shown in Kiro's management console via API. I identified the communication endpoints from the management console's HTML source and observed the actual API calls in CloudTrail. When I sent requests signed with SigV4 to the undocumented API I found, a subscription platform that manages Kiro and Q Developer in a unified way came into view.
Note that the verification in this article was performed on an AWS account opened for a limited period for investigation purposes. AdministratorAccess permissions were used, and it is not an environment intended for permanent operation.
Looking for clues in the dashboard's HTML source
First, let's take a look at the dashboard's HTML source. This is public information that can be checked with the browser's developer tools.

CSP connect-src endpoint analysis
The connect-src directive of the Content Security Policy (CSP) lists the endpoints the dashboard is allowed to communicate with. When I extracted only the endpoints containing amazonaws.com in the browser's DevTools Console, I found 134 of them.
(Capture: list of amazonaws.com endpoints extracted from the CSP connect-src)
Of these, the endpoints related to Kiro management are summarized below.
| Category | Endpoint | Purpose |
|---|---|---|
| codewhisperer | codewhisperer.us-east-1.amazonaws.com | Profile management |
| user-subscriptions | service.user-subscriptions.{region}.amazonaws.com (17 regions) | Subscription management |
| sso / identitystore | sso.{region}.amazonaws.com (17 regions) | Identity Center integration |
| kms | kms.us-east-1.amazonaws.com | Encryption key management |
| secretsmanager | secretsmanager.us-east-1.amazonaws.com | Secrets management |
| pricing | api.pricing.us-east-1.amazonaws.com | Pricing information |
| monitoring | monitoring.us-east-1.amazonaws.com | CloudWatch integration |
| codeconnections | codeconnections.us-east-1.amazonaws.com | Repository integration |
The one to note is user-subscriptions. Endpoints exist in 17 regions, suggesting it plays a central role in subscription management. However, this service name does not appear in AWS's official documentation.
Discovery of an internal codename
Even more interesting information was embedded in the meta[name="tb-data"] tag of the HTML.
The string zorn appears under the keys zornEndpoints and zornServicePrincipal. It is presumed to be the internal codename of the user-subscriptions service, but at this point its true identity is unknown. I also found another string, tangerinebox. This is the telemetry platform of the AWS console.
Feature flags (33)
From meta[id="meta-features-json"], I found 33 feature flags. All of them are enabled: true.
| Category | Number of flags | Examples |
|---|---|---|
| Kiro-specific | 2 | kiro-pricing, kiro-console |
| MCP | 2 | mcp-configuration, mcp-registry-url |
| Derived from Q Developer | 11 | q-extensions, q-agent-for-*, etc. |
| Dashboard/infrastructure | 18 | merge-old-dashboard, cloudzero-plugin, etc. |
There are only 2 Kiro-specific flags. The remaining 31 belong to Q Developer or the dashboard infrastructure. This suggests that Kiro shares Q Developer's management platform almost as is.
Observing the undocumented API with CloudTrail
Now that the CSP analysis has revealed the services being communicated with, next I'll check in CloudTrail which APIs are actually being called.
Filtering method
When you open the AWS console, a large number of APIs for EC2, ResourceGroup and so on run in the background, making it very noisy. Since the CSP analysis told me the names of the services being communicated with, I filtered by EventSource.
aws cloudtrail lookup-events \
--start-time "2026-02-18T18:28:00Z" \
--end-time "2026-02-18T18:37:00Z" \
--region us-east-1 \
--output json \
| jq '[.Events[] | select(.EventSource == "codewhisperer.amazonaws.com" or
.EventSource == "user-subscriptions.amazonaws.com" or
.EventSource == "q.amazonaws.com")]'
Observation results: 3 services, 14 APIs
When accessing the dashboard (18:28-18:37 UTC), I observed 39 events. Of these, the Kiro-related ones were 14 APIs across 3 services.
codewhisperer.amazonaws.com (3 APIs)
| API | Purpose |
|---|---|
ListProfiles |
Profile list |
GetUsageLimits |
Usage limits (origin: AI_EDITOR or KIRO_CLI) |
ListTagsForResource |
Resource tags |
user-subscriptions.amazonaws.com (3 APIs)
| API | Purpose |
|---|---|
ListUserSubscriptions |
★ List of subscriptions for all users |
ListApplicationClaims |
Application claims |
ListClaims |
Claims (identityProvider: BUILDER_ID) |
q.amazonaws.com (8 APIs)
| API | Purpose |
|---|---|
ListDashboardMetrics |
★ Dashboard metrics (dashboardType: KIRO, granularity: DAILY) |
CreateAssignment / UpdateAssignment |
Subscription management |
SendMessage, ListConversations |
Chat |
GetIdentityMetadata |
Identity information |
ListPluginProviders, ListPlugins |
Plugin management |
Calling the API with a SigV4 signature
Why can't we just call it normally?
For ordinary AWS services, you can call them with aws <service> <operation>. However, user-subscriptions and q are undocumented services with no service definition in the AWS CLI, so neither the CLI nor the SDK can be used.
So I apply SigV4 (Signature Version 4), AWS's HTTP request authentication mechanism, by myself.
通常: aws cli → SDK内部でSigV4署名 → HTTPリクエスト → AWSサービス
今回: Python → botocore.auth.SigV4Authで署名 → HTTPリクエスト → 非公開サービス
Implementation
I call it as a path-based Coral API (POST /{OperationName} + JSON body).
from botocore.auth import SigV4Auth
from botocore.awsrequest import AWSRequest
import requests, json, boto3
session = boto3.Session(region_name='us-east-1')
creds = session.get_credentials().get_frozen_credentials()
url = "https://service.user-subscriptions.us-east-1.amazonaws.com/ListUserSubscriptions"
payload = json.dumps({
"instanceArn": "arn:aws:sso:::instance/ssoins-XXXXXXXXXXXXXXXX",
"maxResults": 1000,
"subscriptionRegion": "us-east-1"
})
req = AWSRequest(method='POST', url=url, data=payload,
headers={'Content-Type': 'application/json'})
SigV4Auth(creds, 'user-subscriptions', 'us-east-1').add_auth(req)
resp = requests.post(req.url, headers=dict(req.headers), data=req.body)
print(json.dumps(resp.json(), indent=2))
Note that of the 14 APIs, the only one that I could call successfully was ListUserSubscriptions of user-subscriptions. The codewhisperer ones returned 429 or UnknownOperation, and the q ones returned 500 or UnknownOperation, which showed that different API protocols coexist across the 3 services.
Execution results of ListUserSubscriptions
Retrieving all users across services
All users of Kiro and Q Dev Pro were returned in a single response.
KIRO_ENTERPRISE_PRO: 12ユーザー
ACTIVE: 10人
PENDING: 2人(未ログイン)
This information matches the dashboard's "User subscriptions" screen exactly. Subscription types other than Kiro (such as Q_DEVELOPER_STANDALONE) were also included in the same response. Because this account's Identity Center had both Kiro and Q Developer subscriptions registered, the information on all users of both services was returned together.
Kiro user list (masked)
| User | Subscription | activated | aggregated |
|---|---|---|---|
| user-A | KIRO_ENTERPRISE_PRO | 2025-12-12 | GROUP |
| user-B | KIRO_ENTERPRISE_PRO | 2025-12-04 | GROUP |
| user-C | KIRO_ENTERPRISE_PRO | 2025-12-08 | GROUP |
| user-D | KIRO_ENTERPRISE_PRO | 2025-12-12 | GROUP |
| user-E | KIRO_ENTERPRISE_PRO | 2025-12-05 | GROUP |
| user-F | KIRO_ENTERPRISE_PRO | 2025-12-11 | GROUP |
| user-G | KIRO_ENTERPRISE_PRO | 2026-02-09 | GROUP |
| user-H | KIRO_ENTERPRISE_PRO | 2026-01-01 | INDIVIDUAL_AND_GROUP |
| user-I | KIRO_ENTERPRISE_PRO | 2026-02-12 | GROUP |
| user-J | KIRO_ENTERPRISE_PRO | 2025-12-08 | GROUP |
The true identity of zorn — the unified subscription platform
The true identity of the mysterious internal codename zorn (zornEndpoints, zornServicePrincipal) that I found in the HTML source became clear here.
zorn = the user-subscriptions service. It was the backend platform that manages Kiro and Q Dev Pro subscriptions in a unified way. By calling just one API, all subscriptions across service boundaries were returned.
| Internal name in the API | Meaning | Status |
|---|---|---|
KIRO_ENTERPRISE_PRO |
Kiro PRO ($20/month) | ACTIVE / PENDING |
Q_DEVELOPER_STANDALONE |
Q Developer Pro | ACTIVE |
Q_DEVELOPER_BENEFIT |
Subscription bundled with Q Dev Pro | ACTIVE (GROUP) |
Q_BUSINESS |
Q Business integration slot | PENDING for almost everyone |
While CloudTrail's CreateAssignment / UpdateAssignment use the names Q_DEVELOPER_STANDALONE_PRO / Q_DEVELOPER_STANDALONE_PRO_PLUS, ListUserSubscriptions used its own name, KIRO_ENTERPRISE_PRO. Even for the same subscription, the internal name differs depending on the API operation.
Differences between Kiro and Q Developer subscriptions
Comparing the responses, there were several differences between the subscription systems of Kiro and Q Dev Pro.
Q Developer Pro is automatically granted a bundled subscription called Q_DEVELOPER_BENEFIT, but Kiro users are not granted it. Kiro and Q Dev Pro are separate subscription systems.
aggregatedSubscriptionType, which indicates the assignment method, is GROUP if assigned via an SSO group, and INDIVIDUAL_AND_GROUP if there are both an individual assignment and a group assignment. The latter applies to users who individually upgraded from PRO to PRO+ in the month-end upgrade article.
Also, lastActivityDate was recorded for some subscription types, but it was null for all Kiro users (KIRO_ENTERPRISE_PRO). It seems that Kiro-side usage is not tracked by this API.
Q_BUSINESS is PENDING for all users
Even users who only have a Kiro contract had Q_BUSINESS: PENDING assigned. This is leftover data from when I tried setting up SSO for Amazon Q Business in the past. PENDING refers to a state in which a license slot has been assigned but the user has never accessed the service.
Why do the two services coexist?
The fact that Kiro and Q Dev Pro coexist within the same Identity Center and can be retrieved across services with a single API is presumed to be a result of the gradual migration from CodeWhisperer → Q Developer → Kiro. The backend management platform (zorn) manages multiple subscription types in a unified way, and only the dashboard GUI is separated by service.
Summary
The overall architecture
Behind the dashboard, three services — codewhisperer and q, centered on zorn (user-subscriptions) — work together.
This verification is provided without any guarantee, but being able to directly check the data behind the console via ListUserSubscriptions gave an interesting result that satisfied my technical curiosity.
I got a glimpse of how Kiro and Q Developer Pro are managed on a unified data platform (zorn) in the backend, so when an official management API is provided in the future, I'd like to check my answers against the data structures observed in this article.
