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

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Functionality already exists
Created by Guest
Created on Mar 27, 2017

AWS S3 connector through proxy

System: InfoSphere Metadata Asset Manager
Actor: Client get the data from Amazon cloud

Description: We are trying to get catalog from cloud in IMAM using AWS 3 connector. We are not able to establish the successful connection to cloud and it is throwing below error.

We opened a PMR on how to create a new datasource to connect to Amazon cloud. They suggested a work around but it didn't work. IBM asked us to open an enhancement request.
  • Guest
    Jul 9, 2019

    We encountered a similar issue where datastage S3 connector stage was unable to connect to AWS S3 because of a lack of proxy capability and some of the jars provisioned with the base install on being old. Thankfully, support were able to provide newer jar's to help resolve our issue. Please reach out to support on this.