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
Workspace Connectivity
Created by Guest
Created on Apr 16, 2020

Access AWS Redshift via VPN

Currently WatsonStuidio has to access AWS Redshift via internet (public network). Requirement is to make this communication secured ( by VPN for example)

Needed by Date Dec 31, 2020
  • Admin
    Virginie Grandhaye
    Sep 9, 2020


    It is already possible today. See the comment I got on how to do it :

    Customer can set up Redshift in a VPC, then go to the Watson Studio/CPDaaS UI and select Administer > Cloud Integrations (customer needs to be account owner or manager for this).

    In the page, open 'Firewall configuration' in the upper right. Select CIDR format for IP ranges provided. Then copy each IP range provided there into the inbound rules for the Redshift cluster VPC, allowing inbound traffic from those IP ranges. This will allow Studio/Cloud Pak for Data as a Service APIs and runtimes to make inbound traffic into Redshift without exposing Redshift to the internet to everybody.

    Closing it. Feel free to reopen it if this solution doesn't satisfy your customer.

  • Guest
    May 1, 2020


    Thank you for your comment. I'm not quite familiar with the network in a multi cloud environment though, the thing is currently (1) they have to use a public network between WS and AWS Redshift, and (2) we cannot fix the IP addresss on the WS side. That's whey they have to make thier firewall on the pubic network open to all IP adress, which is against their policy. If either (1) or (2) is reliefed, they no longer have to have this set up with their firewall. I am not sure if 'secure gateway' can relief (1) or (2).

  • Admin
    Virginie Grandhaye
    Apr 17, 2020

    Some connections in WS can have a 'secure gateway' enabled. Amazon Redshift doesn't, but if we add this option, would that satisfy your needs?