This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
The client was experiencing an issue with the recommendations that Cloudability shows. In the Optimize section there is a subsection called Rightsizing, which is where we can see the optimization recommendations based on the resources we have in the cloud. The situation is that he has some recommendations where the resources no longer exist (these resources are created in one day and on the same day they are deleted, also sometimes the resources are created in one day and after three or five days they are deleted), however they continue to appear for these resources. This happens for AWS, Azure and GCP resources.
We are looking for to exclude these recommendations and only take those with current resources.
For the above reason, we request, based on the support response, that the request for ec2 permissions be added: DescribeInstances permission to be provided for all AWS linked accounts, which would be needed to determine whether a given instance was explicitly terminated.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Hello, I believe there is already a setting available for this. Under the Settings menu, go to Rightsizing Preferences. On that page there is a setting for "Resource Lifespan". Setting that value to 1, for example, will exclude recommendations for resources that have been inactive for 1 day.
By default, our Compute recommendations (EC2 / Azure Compute / GCP) currently include all resources that existed at any time in the lookback period (10 or 30 days) and for which money-saving recommendations can be provided. The primary reason we do this is that including all resources with potential savings gives the customer a complete picture of the total cost/savings that would have been possible in the time period if all resources that existed during the period had been terminated or sized as recommended. In particular, this helps identify the full cost / savings of short-lived instances that may be automatically created through various automated mechanisms.