57 results found
-
Flexsave for RDS/Databases
Please reinstate and expand DoIT's Flexsave for RDS/Databases option. AWS's recent announcement of Database Savings Plans should help DoIT mitigate the risks of unused capacity and make Flexsave for RDS/Databases feasible. Ideally, Flexsave for RDS/Databases should work similarly to Flexsave for Compute.
2 votes -
Reinstate and expand Flexsave for Databases
Please reinstate and expand DoIT's Flexsave for RDS/Databases option. AWS's recent announcement of Database Savings Plans should greatly help DoIT mitigate the risks of unused capacity.
2 votes -
Invoice API, download the PDF invoice
Can we have an additional Invoice API to get the actual invoice PDF files?
2 votesDue to previously planned work for the remainder of the year and into January, this work is slated for Q1 / early Q2 of 2026.
-
Creating bulk edit capabilities in the portal for biz ops
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 integrations2 votesDue to previously planned work for the remainder of the year and into January, this work is slated for Q1 / early Q2 of 2026.
-
Adding an estimated "bill without DoiT" comparison to the Invoice Explainer to clarify savings for customers
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 -
Custom Import Filters for Cloud Account Onboarding in Cloud Diagrams
Allow users to customize the import settings during Cloud Account onboarding.
Users should be able to filter resources based on:
* Region (e.g., import only us-west-2)
* VPC (e.g., focus on specific VPCs for diagram clarity)
* Tags or Allocations (e.g., import only resources tagged with Environment=Production or belonging to a specific team)
* Resource Name Patterns (Regex Support) (e.g., import only resources with names matching .-prod-.)User Value: This feature will provide more control over what gets imported into Cloud Diagrams, helping reduce visual clutter and improving relevance, especially for large environments. It also supports security and scoping…
2 votes -
Ability to detect anomaly on monthly cost granularity
If there is a gradual increase in cost on daly basis such increase will not be considered as an anomaly as the data would look like an expected increase however if we compare this cost over month to month the increase can be significant. Hence it is worth generating anomalies on such cost spikes on Monthly granularity.
2 votesIn backlog, pending PM Discovery
-
Add exchange rate pricing to billing column in reporting
Add exchange rate pricing to billing column in reporting
2 votes -
BigQuery Untagged spend insight
We should provide “Insight” on untagged BigQuery spend. Something like “xx% of your BigQuery queries is not labeled/tagged
2 votes -
Managing CUDs / spend reservations
A tool in the UI to manage CUDs / spend reservations. It’s currently fairly manual, and the out-of-the-box tools AWS and GCP provide don’t entirely help.
2 votes -
Filter Insights by Attribution
As an individual on a team or working on a specific product, I'd like to see which portion of my company's total insights can be implemented by my team. This helps me understand which cost opt / security recommendations are within my team's control.
Similar concept to why we allow users to filter for anomaly alerts by an Attribution or might recommend customers to create customers dashboards made up of reports that are filtered to an Attribution (rather than looking at a Lens). Less noise + I know what I can take action on immediately. I believe this would also…
2 votes -
flexsave account ou sorting iac
If you're going to provide lambda/policy/eventbridge config to organize OUs automatically when FlexSave accounts are added to the org, you might as well provide some IAC (terraform/cloudformation) to deploy it.
Thanks2 votes -
Search box for Actions in Cloudflow
When creating a node, the amount of options might be overwhelming, especially if the customer doesn't know exactly their intent. If we add a search box that returns the actions for each box, it would help the customer discovery in cloudflow capabilities.
1 vote -
DCI CloudFlow FinOps Trigger or Node
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 history1 vote -
Invoice Dispute Visibility for Collections
Description
Introduce a mechanism that allows invoices with active customer disputes or open invoicing / PSS support tickets to be clearly tagged or flagged within DoiT’s billing systems.Purpose
This would give the Collections team immediate visibility that an invoice is already under investigation, enabling them to:temporarily pause follow-up or escalation actions, or
adjust the tone and context of automated collection emails while the issue is unresolved.
Why this matters
Without dispute visibility, automated collections may trigger escalation messaging that is misaligned with the actual invoice status, creating unnecessary customer friction and confusion—especially for trusted, long-standing accounts.Outcome
Improved…1 vote -
Smart Alerts for directly to relevant teams\groups\units
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 -
Console Support for Raising Internal PSS Request and Selection of Ticket Privacy Mode
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 customerPlease 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 -
Increase Analytics filter/group-by dialog limit beyond 5000 resource values
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 -
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 voteReviewing this request to understand options for successfully implementing this idea.
-
Enforce SSO for admins
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
- Don't see your idea?