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

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

62 results found

  1. Add a FinOps trigger/node responsible for configuring and enforcing budgets/limits for automations (Guardrail). This node should allow users to:

    Define budget thresholds (per project/account, tag, or flow)
    Set hard/soft limits for automated actions (e.g., stop, throttle, require approval)
    Trigger alerts or approvals when thresholds are reached or exceeded
    Expose configuration and status clearly in the UI and run history

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Today we have real-time anomaly detection - rich with info, great to use and investigate, but get's dumped in to a shared slcak channel with 10s of people
    We tried building the cost alerts, did it with allocations we build in doit for each group, and sending by email to a dedicated slack channel. But we got a lot of false positives with it . we can only decide if it alerts on a % change or actual $ change. we only want to follow % change, but doing it without a min $ threshold to alerts just notified us…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Currently, the Cost Anomaly feature is designed to capture spikes in spend but does not monitor for dips. Similarly, the Alerts feature works on defined thresholds, which is more suitable for catching increases than decreases.

    It would be valuable to have a feature that can detect sudden drops in cost as well, since unexpected decreases can also indicate issues such as:

    Disabled services or resources that should be running

    Failures in data pipelines or workloads

    Gaps in logging/monitoring or data ingestion

    Sudden deletion in data

    Adding anomaly detection for dips would provide a more complete view of cost changes and…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Enable integration with AWS CloudTrail to fetch near real-time infrastructure change logs. Additionally, by linking each change event to the specific IAM role or user that made the modification, teams gain clearer accountability and traceability.

    User Benefit:
    * Gain near real-time visibility into infrastructure changes
    * Enhance team accountability by identifying which IAM role/user made each change
    * Keep precise audit log that's easy to read and won't miss small transient changes. This will help with compliance and internal governance for enterprise customers

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. To support the proposed console integration of internal PSS support flow, we'd like the Console's Expert Inquiry to support the following:
    - recognise "visibility" attribute to determine if a product should be hidden from customer in the dropdown list
    - when a Doer is creating a new request under a customer tenant, a pop up dialog should be presented for the Doer to select whether the ticket will be private or viewable by the customer

    Please refer to the following requirement document for more details, including tags, assignee and UI mock-ups: https://doitintl.atlassian.net/wiki/spaces/fde/pages/1623883778/DoiT+Console+PSS+Internal+Request+Flow+Requirements

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    In Backlog  ·  0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Current behavior
    In Cloud Analytics reports, when using the filter or group-by control on resource ID, the selection dialog only lists up to 5000 distinct resource values. As a result, specific resource IDs that are visible in the report table (may not appear in the selection dialog and cannot be filtered or grouped on, even though they are present in the dataset.

    Impact
    This prevents customers from reliably drilling down to specific resources at scale, blocking important FinOps and DevOps optimization workflows. Customers are forced to export data to external tools to achieve the required level of granularity, which creates…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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)

    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)
  9. Hi, Can you create a GCP committed usage discount expiry report?

    22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  1 comment  ·  Budgets & Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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)

    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)

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

  11. Is there a way to look at creating a mechanism where sales can make bulk account ownership changes?

    We are currently dependent on scripts to make changes and there are times the urgency doesn't match the availability of engineers.

    Can we either:
    Get access to run the script
    Develop a function in the console that allows us to bulk update
    Allow us to assign account ownership in SFDC and replicate to the console via integrations

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

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

  12. Description:
    Users would like the ability to view aggregated cost data for resource groups in Cloud Diagrams, not just individual resources. For example, clicking on an ECS cluster should display the total grouped cost of all its sub-resources.

    Use Case:
    This would help teams quickly assess the total cost impact of a service or component (like an ECS cluster or auto-scaling group) without manually summing individual resource costs.

    Requested By:
    Flavio Alberti (THRON)

    Impact:
    Improves financial visibility and supports more accurate cost analysis directly from the diagram view.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Currently, all admins bypass SSO completely, which is a security gap since those sensitive accounts are the ones we need to be secured the most. I understand the use case for having a breakglass account, but making all admins bypass it with no way to enforce it defeats the purpose of having SSO enabled to begin with.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Currently, when searching for an AWS account or GCP project, the result is just a static link to the asset details page. To check costs or settings, I have to click the result, wait for the page to load, and then navigate through menus again.

    Please make the search results more dynamic by adding "Quick Actions" directly in the dropdown. When I search for an asset ID, I would like to see buttons to:

    Open a Cost Report filtered specifically for that account.

    Go directly to the Cloud Flow or Attribution settings for that account.

    This would significantly reduce the…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Allow for invoices to have "Invoice period" column which you can sort by. When you reissue an invoice that information does not exist or gets lost. All invoices should have (mandatory, by law) an explicit period listed for which the invoice is charged.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Add a button next to invoice to more easily raise an issue around that invoice.

    Should help with speeding up payments.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    • Get a daily/weekly email with a combined summary of changes since the prior week

    • Use the DoIt API to get a list of changes/history that is currently displayed in the UI

    • Get notifications of changes, such as a slack webhook that fires any time a new snapshot/change is created

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Is there any chance if we can test on the GCP Marketplace if we can offer DoiT's DCI offering as an all upfront payment?

    A customer would be very keen to do this and we have the contractual mechanism on this side.

    Some Google teams have suggested it wouldn't be possible but Sebastian based on what he could see, seemed to think it would be possible

    Per House BP:
    Assuming all upfront means annual payment, I see that it is possible to create a private offer for such. However our backend doesn't support annual, so some refinement and development would…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

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

  18. There is a request to add an estimated 'bill without DoiT' directly into the Invoice Explainer. Currently, customers struggle to see the value we provide because they can only view the AWS bill to DoiT and the DoiT bill to them. We also need to know how many are using the console reporting to see their savings. This lack of transparency on the invoice creates confusion, particularly around renewals, leading to the impression of overpayment and potentially jeopardizing customer trust. By including a 'bill without DoiT' comparison, we can clearly demonstrate the savings and prevent this recurring issue, ultimately improving…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Bigquery Lens should have reports going back more than 30 days. I believe at least 3 months would be sufficient to see usage changes and activity.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?