This is an IBM Automation portal for Integration 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.
Hi.
Yes, ASG (AWS Auto Scaling) is an example of this. For example, we have an Auto-Scaling group configured for Min. 2, Preferred 3 & Max 5. The high water mark can ONLY ever be 5 as it represents the maximum number of instances that can be active at one time. This is also what we should be licensed for.
Here is a standard scenario that most organizations using ASG would encounter. This is where ILMT has all the data but fails to apply the correct count (high water mark) leading to issues.
Day 1 - we scale to Max 5. (High water mark established & should comply with our license entitlement)
Day 2 - at 2am we terminate them all. At 4am we spin up 3 (Preferred) new ones at the start of the new day.
High water mark is still 5 but ILMT now says it's 8! The expotential growth continues indefinitely. We can tag the EC2 instances with a name to relate them to a specific ASG but ILMT is counting based on unique hostname. Since the hostname changes for every individual instance then ILMT cannot group them and apply rules associated with the ASG. Trying to force a design change on AWS ASGs (not even sure how that would work) to comply with ILMT existing rules makes no sense.