Skip to content

DoiT Cloud Intelligence

Welcome to Customer Voice!

Have an idea? Share it. Your feedback directly shapes our roadmap.

Tell us the problem you’re facing and what your ideal solution looks like. The more specific you are, the faster we can act.

DoiT Cloud Intelligence

Categories

How can we improve DoiT Cloud Intelligence™?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

4 results found

  1. Add acknowledgement and alert dates to Cost Anomalies API

    Would it be possible to add new fields to the data returned by Anomalies API? Namely:
    - acknowledgement timestamp
    - first notification sent timestamp (as this is not the same as anomaly start)

    These pieces of data are critical for tracking internal SLAs on cost anomalies but are currently missing and have to be inferred and approximated from other sources.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  APIs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Refinement/Prioritization  ·  AdminNikola (Admin, DoiT) responded

    Thanks for submitting this idea!


    This is a quick confirmation that we will review this in the near future.


    Preliminary comments:

    • The Acknowledgment timestamp sounds like a straightforward improvement.
    • The timestamp of the first notification sent could get more nuanced, as a single anomaly could be sent to multiple channels, so we will aim for a solution that would be both feasible to implement and valuable for customers.

  2. 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

    6 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. 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…

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Invoice API, download the PDF invoice

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

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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.

  • Don't see your idea?