Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
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
Created by Guest
Created on Oct 3, 2025

wxO & IBM SaaS console should track, list and manage API keys made on AWS platform

On AWS, after creating a new API key, there is no way to track,  list or manage the API keys.

According to our documentation,

"Managing the user API key - Accessing the list of API keys"
https://www.ibm.com/docs/en/watsonx/saas?topic=administration-managing-user-api-key#accessing-the-list-of-api-keys

It mentions:

> On AWS, you don't have access to your user API keys from the IBM SaaS console.

Because there is a limit of 10 API keys per user, this essentially means AWS users have to keep track of all API keys themselves, outside of the user interface.  This is cumbersome and more prone to errors or misplacing / losing the API keys list.

Idea priority Medium