Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management 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.

Status Under review
Workspace IBM Turbonomic ARM
Categories Public Cloud IaaS
Created by Guest
Created on Jan 26, 2024

Put a configurable cap on concurrent automated actions for the cloud provider to help with throttling.

The client is experiencing AWS throttling for EC2 Scaling Actions. 1000 actions can happen at the same time but can fail mid action due to AWS Throttling. . There is a setting called " properties:     action-orchestrator:          actionExecution.concurrentAutomatedActions: 50 " which can cap the total concurrent actions - BUT we don't want this to extend to ALL automated actions. The client also has on prem WPA actions which we don't want to cap.  

I would like to be able to constrain JUST THE AWS actions to let's say 50 concurrent actions - to help with throttling. How this happens is not important. But I would suggest EITHER a specific parameter in YAML like actionExecution.concurrentAWSAutomatedActions:  OR more conveniently (so we don't have to edit the yaml) put the cap into the Automation Policies.  Set Concurrent Actions to 50 for a particular SCOPE - maybe just AWS or Just Azure etc etc. 

Idea priority High