Datasource creation failed

Question & Answer
, ,
1

I’m trying to import a dataset into another account using the next start-asset-bundle-import-job and I’m running into this error with the datasource

image
image1227×514 22 KB

Does anyone know how to increase the time limit for the data source validation or another way to fix this error? I’ve increased the cli-read-timeout on the start-asset-bundle-import-job but that doesn’t fix the issue.

2

Hi @ineedqshelp

Could you please confirm:

  1. If the QuickSight role on the destination AWS account has relevant permissions to access RDS?

  2. Are you able to create a data source connecting to this Aurora instance through the QuickSight console on the destination account?

2 Likes
3

Hi @ineedqshelp - From error, it looks like there is an issue in connectivity with db in the target account. Can you describe data set in the target account and get those connectivity details. The suggestion by @SD_QS is correct.

Regards - Sanjeeb

1 Like
4

What is RDS? I will try the data source connetion.

5

The dataset wasn’t created, so I can’t run describe data set in the target account.

6

I was referring to the RDS service of which Aurora is a part :slight_smile: Fully Managed Relational Database - Amazon RDS - Amazon Web Services

2 Likes
7

Hi @ineedqshelp - Sorry, I mean the data source, can you please describe data sources and ensure you have the connectivity from QuickSight?

Regards - Sanjeeb

1 Like
8

There is connectivity, here’s one created manually first, the one on the bottom is created through the commands.

image
image1451×1006 27 KB

9

@ineedqshelp from the screenshot, clearly the type of the data source “POSTGRESQL” in the manually created section is different from “AURORA_POSTGRESQL” in the section being attempted via asset import job…

The fastest way for you to be able to resolve this would be filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!

5 Likes
10

Hi @ineedqshelp - I agree with @SD_QS , a support ticket will help in resolving the problem. Also since the data source is created programmatically, can you please ensure you have test the connectivity. You can do this by login to QuickSight UI-> data sets → New data sets → open the data source ( which will be in the bottom) and do a test connectivity. This is to ensure you have no issue with connection.

Regards - Sanjeeb

2 Likes