Skip to main content
Telara

Integrations / Amazon Q Developer

Amazon Q Developer logo

Amazon Q Developer

Amazon Q Developer — account-level adoption metrics (invocations, active users, generated lines) via CloudWatch. Spend connector for the AI Platform Spend Governance feature.

API key
Spend
AI estate

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI YesRuns actions NoReal-time events No

Before you connect

Prerequisites

An AWS account where Amazon Q Developer is enabled.
IAM permission to create a user (or role) and attach CloudWatch read access. Do not reuse a human console login.

Vendor setup

Get the credential

1
Create a dedicated IAM user
In the AWS console, go to IAM → Users → Create user. Name it for Telara. Skip console access.
2
Attach CloudWatch read access
On the user, open Permissions → Add permissions → Attach policies directly. Grant the CloudWatch permissions this page lists from the catalog. Telara reads Q Developer metrics; it does not need to start Q sessions.
3
Create an access key
Open the user’s Security credentials tab → Create access key → Other. Copy the access key ID and secret. AWS will not show the secret again. Paste them under Settings → Integrations → Amazon Q Developer, with the region Q is emitting metrics in (often us-east-1).

In Telara

Connect in Telara

API key

AWS IAM access key with cloudwatch:GetMetricData permission (read-only). Store aws_region (default us-east-1).

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • Aws Access Key Id
  • Aws Secret Access Key

Spend

What gets measured

Resolution: Aggregated buckets.

Attribution: Matched to people by the vendor user id.

How far back vendor history goes is not published uniformly for this connector.

  • invocations
    count
  • active_users
    users
  • lines_generated
    lines

AI estate

What gets discovered

Config paths
  • ~/.aws/amazonq/mcp.json
Resource kinds

mcp_client_configuration, mcp_server_deployment

Config paths
  • .amazonq/mcp.json
Resource kinds

mcp_client_configuration, mcp_server_deployment

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

Q Developer metrics only appear after logging is enabled for that AWS account. An empty chart is usually missing CloudWatch metrics, not a bad key.
SSO / IAM Identity Center still needs a dedicated machine user. A human SSO session is not a connector credential.