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.

Status Planned for future release
Created by Guest
Created on Jan 15, 2024

AWS discovery sensor to support AWS temporary credentials, not just long term credentials

There are 2 types of credentials available when accessing AWS' public URL - temporary, and long term.

My organisation, in consultation with AWS, have implemented an AWS security policy that only allows the use of temporary access credentials.
Since TADDM does not support this type of crednetial, it has resulted in TADDM not being able to discovery AWS devices.
This has greatly impacted the relevance of the CMDB data within my organisation, as it is not able to identify the infrastrcuture supporting some of our most critical business applications.

My organisation is not really one to establish configurations that are not following what is considered best practice. So I would be assuming that this issue is affecting a number of other organisations utilising TADDM and AWS.

Can you please consider developing the AWS discovery sensor so that it also supports temporary credentials?

Idea priority Urgent