Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Submitted
Workspace StreamSets
Created by Guest
Created on Jan 11, 2025

Enable AWS Secret Manager credentailstores to assume the IAM Role of an k8s serviceAccount

Currently, there is a limitation with SDC credentialstores when SDC runs in EKS. When SDC accesses AWS Secrets Manager via the credentialstore functions and the authentication configured in credential-stores.properties is instanceProfile, the role which SDC will try accessing these secrets will be the IAM Role of the k8s pod, rather than the serviceAccount role.

This is problematic since:

  1. The ideal role which should be assumed is the configured serviceAccount.
  2. It's also a different behavior than when AWS stages assume the default instanceProfile. For instance, AWS stage in the pipeline are able to assume the serviceAccount IAM role, it's only our credentialstore functions which are assuming this k8s pod's IAM role.
  3. Using IAM Roles instead of AWS keys is often a security policy requirement in live environments, so there is no secure workaround to get the assumed role working for credentialstores.

Ideally we should support k8s deployments having same secure AWS instanceProfile authentication options for credential stores, and some way for customer's to use their same serviceAccount's IAM role that their other AWS stages are able to assume.

Needed By Quarter