62 results found
-
PLPS cancelation ticket routing
There is a dropdown option in the DoiT Console called “Partner Led Premium Support - Cancellation Request”. This currently routes the ticket to PSS. This should instead route the ticket to the zendesk group “AWS/GCP Support level questions”
Impact: Today sales reps have to submit a getdoer and apply the support level macro so it’s routed to the team. This creates more work for the reps if there is already an option in the console1 vote -
Add PerfectScale contract to the console
fields:
start date
end date
vcpu hours #
unit price $
Because we can't bill PS through the console, finance wants a notification of every Perfectscale agreement that is signed so finance can manually bill them.Avalon will need to add more specific details once she knows how invoices are supposed to be automated through this system.
1 vote -
Allow multiple documents to be added to contract in console
Currently when you upload a contract to the console, you can only upload one document. This request is to allow multiple documents (at least two) so that when there is an amendment, that document can be included in the contract set.
This would be applicable for both customer contracts & vendor contractsImpact: If we upload an amendment, it will overwrite the original contract, so we’ll have no visibility into the original contract.
1 vote -
Add Azure discounts into console
There is currently no option to add a discount to an Azure contract. While we don’t get very many, the current workflow requires manual invoicing until this is resolved.
1 vote -
Add auto-renewal box for commits
Similar to the request to add an auto renewal box for DCI contracts. We would like to add a tick box under AWS/GCP commits for “Contract Auto-Renewal”. When the contract expires, a new OD (On-Demand) contract would be created automatically so an active contract is in place since we’ll continue to bill the customer until they either sign a new contract or terminate.
This would then prevent customers losing access unnecessarily if renewals are delayed or contracts have been signed with an effective date after the end date of the previous contract, increase customer renewal experience, and alleviate the manual…
1 vote -
Adjust the AWS "Cost by Service" visualization to reflect Net Cost.
Adjust the AWS "Cost by Service" visualization to reflect Net Cost.
Currently, private rate discounts are appearing as negative line items; these should be factored into the service totals so the graphs display the actual spend after all discounts have been applied.
16 votesChatting with TPOs & BP&O to see what this might mean for us.
-
New Navigation
New Navigation is a little bit confusing. Maybe it's just me but I have a hard times finding what I need. Before everything was in one place (horizontal links in navbar) and now it's hidden behind the menu which feels very heavy and each time I end up looking for the link
1 voteThank you for your feedback! To mitigate the impact of this change, please note that now you're able to set Favourites in DCI.
Hovering next to a menu item shows the ability to pin that item in the top bar, for even faster access to the DCI sections most relevant for you.
Also the new navigation has a "Recently Visited" section as well.
Looking forward to hearing you how you're finding it
-
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 -
Support direct integration with Statsig in Cost Intelligence
Support integration of Statsig cost, just like databricks, mongo and other 3rd parties.
Statsig is quite expensive and usage base so cost visibility, monitoring and alerting in a single pane is valuable2 votes -
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 -
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 votereaching out to the customer for further details
-
Provide option to apply Heatmap to Absolute and/or Percentage Change columns only
When Absolute or Percentage Change is selected for a report, an option to apply the Heatmap to only those columns should be available.
Current behavior applies heatmap logic and color coding to every value present in the table, making it impossible to quickly identify cost drivers or savings by these change values.
2 votes -
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 -
Add AWS account status to the Assets page
The AWS assets page currently shows all accounts but there is no way of knowing if the account has been closed. We should add the AWS status/state of the account and not show closed accounts in areas like CloudFlow or CloudConnect.
2 votesLooks like a quick win for customers. Researching on what is the best approach
-
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 -
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.
-
Account alias column in insights table
On the insights detail pages, it would be nice to have a column for the account alias in the table. So I can see [Redacted Account Name] instead of just [Redacted Account Number].
6 votesThanks for this idea! We've already had this in mind and this feedback helps us prioritize it – we will implement this within the next few weeks.
-
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?