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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Created by Guest
Created on Jun 19, 2024

Authentication mechanism used for the AWS Observer

One of our customer has a security policy in place, that enforces the following mechanism to be used when accessing AWS:

The mechanism is to assume an IAM role in the AWS account using the  'sts:AssumeRoleWithSAML' AWS API call. This returns a set of temporary AWS security credentials (aws access key id  / secret access key / session token) for users who have been authenticated via a SAML authentication response.

The SAML 2.0 authentication is done by customer's Azure IdP - so,  a 'service account' user would need to be created in the Azure AD for this purpose. The service account user would be made a member of an AD group which authorises the user to assume the relevant IAM role.


Currently, only Access and secret key is used. If we cannot comply with this requirement, we'll need to get a security exception which involves a tremendous amount of work, which we want to prevent.

Idea priority High