- Newest
- Most votes
- Most comments
Hello, I see that you are trying to use GDS with your RDS instance. You have mentioned that you instance is private and when you try connecting with GDS it asks it asks for server and client certificates and as well as a client private key. However it seems that RDS does not allow customers to upload nor configure their own certificates. With that being said RDS maintains its own certificates on the hosts. Customers who would like to use SSL must download the RDS specific regional root certificates[1], which is mentioned in the documentation[2]. Note that if your application does accept certificate chains, you can may use a root certificate that works for all regions[1]. However you can connect with your instance publicly or privately accessible using the google 3rd party partner connectors like 2minute Report which you can use for select queries because you can use the SSH option to connect. AWS RDS is a managed service and only needs RDS specific SSL certificates provided in the documentation the issue you face is direct at GDS configurations which requests you to provide an additional SSL certificate and private key. Currently there are no clear directions by Google on how to connect to Amazon RDS database instances from Google Data Studio, with SSL enabled but I have found a helping method to do so[3].I have also found the thread[4] that is present on the Google support community that mentions that it is not possible to connect to the RDS instance through SSL. You can refer the same thread for your reference. However, you may still use Google Data Studio to connect to your RDS/Aurora without SSL if your use case permits. Due to this in a private subnet, I found these IP's from Google's documentation that you need to have mentioned in the security group[5]. Once you have these changes, attempt to do the connection. Google IPs: 64.18.0.0/20 64.233.160.0/19 66.102.0.0/20 66.249.80.0/20 72.14.192.0/18 74.125.0.0/16 108.177.8.0/21 173.194.0.0/16 207.126.144.0/20 209.85.128.0/17 216.58.192.0/19 216.239.32.0/19
References: [1] https://truststore.pki.rds.amazonaws.com/global/global-bundle.pem
[2] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.SSL.html
[4] https://support.google.com/datastudio/thread/18683032?hl=en
I'm not sure, but you can try Skyvia as an alternative solution. It is a no-code cloud ETL tool.
Relevant content
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
Hello @Antonio. I am glad at last someone respond. I read out your comments & i appreciate it. But problem is , the solution you provide i already test it, & this solution is for public DB not for private. As my RDS is in private subnet, it's not possible to figure it out by GDS. In that case how can i connect it? One of my team mate said to use open vpn, but in GDS i cant figure it out how to install/configure vpn on GDS?
We are also in the exact same situation. @rePost-User-9120760, did you ever come up with a solution? Our RDS is on private subnets, but need to grant access to Google Looker Studio.