4 results found

1. Allow an anomaly's status to be updated programmatically via the API.

   The Anomalies API is currently read-only (GET /analytics/v1/anomalies and GET .../anomalies/{id}). There is no way to change the state of an anomaly through the API.

   Please add a write path - for example PATCH /analytics/v1/anomalies/{id} -supporting an acknowledge / dismiss / resolve state transition, ideally with an optional note or external-reference field so an anomaly can be linked to a record in an external system. This would mirror the status-update capability the Insights API already provides via PATCH /insights/v1/sources/{sourceID}/insights/{insightKey}.

   This may also merit adding another endpoint to the API for listing ackowledement reasons.

   Use case:
   Teams that automate FinOps workflows need to reflect an anomaly's resolution back in DoiT once it has been handled elsewhere. Without a write path, anomaly state can only be tracked outside DoiT, so the two views drift apart and the same anomaly gets reviewed repeatedly. A simple status write-back keeps DoiT aligned with downstream automation and avoids duplicate triage.

   The Anomalies API is currently read-only (GET /analytics/v1/anomalies and GET .../anomalies/{id}). There is no way to change the state of an anomaly through the API.

   Please add a write path - for example PATCH /analytics/v1/anomalies/{id} -supporting an acknowledge / dismiss / resolve state transition, ideally with an optional note or external-reference field so an anomaly can be linked to a record in an external system. This would mirror the status-update capability the Insights API already provides via PATCH /insights/v1/sources/{sourceID}/insights/{insightKey}.

   This may also merit adding another endpoint to the API for listing ackowledement reasons.

   Use case:
   Teams that… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Planned  ·  0 comments  ·  APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Programmatic API to link AWS accounts and enable Kubernetes core (incl. bulk operations)

   Customers with many AWS accounts need a fully programmatic way to complete the DoiT “Link account” + Kubernetes core enablement flow, especially during the EKS Intelligence → Kubernetes Intelligence migration. Today this must be done via the Console/CloudFormation flow and cannot be completed end‑to‑end via public APIs, creating manual work and coordination overhead for multi‑account orgs. The current Console flow relies on CloudFormation plus a backend webhook/validation step to register the role and mark features as enabled; this callback is not exposed publicly, so adding IAM permissions with Terraform alone doesn’t flip the feature state. As a result, there is no public, automated path to link accounts or enable Kubernetes core across many sub‑accounts.

   Customers with many AWS accounts need a fully programmatic way to complete the DoiT “Link account” + Kubernetes core enablement flow, especially during the EKS Intelligence → Kubernetes Intelligence migration. Today this must be done via the Console/CloudFormation flow and cannot be completed end‑to‑end via public APIs, creating manual work and coordination overhead for multi‑account orgs. The current Console flow relies on CloudFormation plus a backend webhook/validation step to register the role and mark features as enabled; this callback is not exposed publicly, so adding IAM permissions with Terraform alone doesn’t flip the feature state. As a result, there is… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Discovery  ·  AdminTony (Admin, DoiT) responded

   Reviewing this request to understand options for successfully implementing this idea.

3. Service accounts for API use

   Hello,

   It'll be a good feature to be able to create read-only API keys, so the API access can be automated with less risk.

   Thanks

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  2 comments  ·  APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Invoice API, download the PDF invoice

   Can we have an additional Invoice API to get the actual invoice PDF files?

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Planned  ·  AdminDewey (Admin, DoiT) responded

   Due to previously planned work for the remainder of the year and into January, this work is slated for Q1 / early Q2 of 2026.