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,
Post an idea
Upvote ideas that matter most to you
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.
Data Catalog dynamic IP address frustrates IP address security filters in remote clouds and on-premise systems.
I'm testing the Data Catalog's ability to access a remote(to IBM's cloud) relational database. I provisioned a NoSQL database using AWS RDS service. I wanted to set the AWS security group to only permit access from the IP address used by the Data Catalog. I used AWS logging to determine the IP address used by Data Catalog and set the security group to permit access from that IP. Data Catalog was able to access the MySQL database and access the data. However, the next day it stopped working. Reviewing the access logs on AWS showed the IP address used by the Data Catalog had changed. I tried this several different times and at some point the IP address of the Data Catalog would change (the "From" address as seen by the AWS security group.) The class-A subnet also changed making it impossible to create a generic IBM cloud filter. I realize IP addresses are a bad approach but, unfortunately, are in use as security filters by clouds and on-premise systems.
Is there any way to specify a public IP address for the Data Catalog to use that doesn't change?
I don't know if the observed behavior is coming from Data Catalog or the networking layer of Bluemix and/or Softlayer.
My next step is to try setting up a Security Gateway between Bluemix and AWS with the idea I can get the Data Catalog to use the Security Gateway to tunnel over to a virtual lan segment at AWS where the database resides.
Do not place IBM confidential, company confidential, or personal information into any field.