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.
Why is it useful?
|Who would benefit from this IDEA?||As a customer I want to access an on-premise or remote cloud protected by IP address based security filtering|
How should it work?
|Submitting Organization||F2F Sales|