Feature Requests

Description Currently, Cloud Custodian does not support AWS DMS replication instances (aws.dms-instance) as a resource type. Due to this limitation, we are unable to implement governance and cost optimization policies for DMS replication instances. Use Case Customer requirement to identify idle DMS replication instances: Instances with no associated replication tasks Instances that are unused/idle for >30 days Include these in recommendations for cleanup or cost optimization At present, this use case cannot be achieved since the resource type is not supported in Custodian. Expected Outcome Add support for aws.dms-instance in Cloud Custodian Enable filtering based on: Instance attributes (ARN, status, creation time, etc.) Association with replication tasks Support standard actions like: Notify Tag Delete

Customers with large Azure subscriptions (greater than 80,000 resources) are impacted due to ARM limitations, which prevents retrieval of tags in autostopping rules. Introduce support for Azure Resource Graph as an alternative data source for querying resources. Azure Resource Graph is designed for large-scale resource querying and does not have the same limitations as ARM in this context.

Description: Please consider enhancing the recommendation output for unattached EBS volumes so results can be grouped at the cloud account level rather than only at the individual resource level. At present, recommendations for unattached EBS volumes are evaluated and surfaced per resource. In larger environments, it would be helpful to support an aggregated view where a single recommendation can represent an account and include the list of matching volumes associated with it. Requested enhancement: Add support for recommendation grouping/output that can: • aggregate matching unattached EBS volumes by account • display one recommendation per account • include the list of matched resources within that recommendation Why this would help: This would make recommendations easier to review and manage at scale, especially in environments with many matching resources. It would also provide a more consistent summary view for governance and cleanup workflows. Current rule example: policies: - name: delete-unattached-aws-ebs resource: ebs filters: - Attachments: [] - State: available actions: - delete Current limitation: While the rule can identify the matching resources, the recommendation output does not currently provide an aggregated account-level representation with a list of all matched resources.

i can see below recommendation shows that it does not exists anymore https://app.harness.io/ng/account/vGS8Qq_fSJik8VyI4rwqHQ/module/ce/recommendations/ec2/66a1b40ecf6ab2e87b58b9ec/name/r6i.xlarge%20(i-013564dac135fd778)/details however we have an associated ticket , but there is no action being taken by harness yet , we can still see the ticket is open yet.

There is no native feature that provides recommendations based on Azure Reserved Instances (RI) or Azure Savings Plans. Request: Enhance the CCM (Cloud Cost Management) module to: Provide savings recommendations based on Azure Reserved Instances. Provide savings recommendations based on Azure Savings Plans.

Currently if a Harness customer has Hybrid Benefit/Enterprise Agreement/MAC, the pricing and savings shown in Recommendations can be as far as 50% higher than what it actually is, which can affect decision making. We would like Harness to poll Azure for the correct customer pricing per VM SKU, so the prices and savings shown are accurate for that customer.

We want support for Ingresses managed by AWS Load Balancer Support for auto-stopping via EKS CCM