Skip to Main Content
Cloud Management and AIOps


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).

Shape the future of IBM!

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

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.

Workspace IBM Turbonomic ARM
Categories Policies
Created by Guest
Created on Dec 28, 2023

Automatic policy creation for instance type scale that take Availability Zones into consideration.

Sometimes, we encounter the error 'The requested configuration is currently not supported.' due to the instance scaling action.

 

Example: t3.micro -> t3a.nano

 

Regions where each instance type is supported:

    t3.micro:  ap-northeast-1d, ap-northeast-1c, ap-northeast-1a

    t3a.nano:  ap-northeast-1d, ap-northeast-1a

 

In this case, if the original instance was located in ap-northeast-1c, the changed instance would not start due to the error: The requested configuration is currently not supported.

It may be a rare pattern, but I would appreciate it if such regional restrictions could also be automatically created as policies.

Idea priority Low