the boto3 API has had the “asset_bundle_export/import_job” functions for several months. I am currently trying to migrate a Snowflake asset including an analysis, dataset and datasource to another account. The export works without any problems. When importing, I noticed that I have to adjust the VPN configuration in the AssetBundle so that the datasource works in the target account, otherwise I get errors that the subnets are not recognised. I have solved this problem by overriding the VPNConnectionJson with configuration from the target account. So if I import the analysis alone, it works without any problems. However unfortunately not if I try to import all other assets as well. I get the error message:
Response
{
“statusCode”: 500,
“body”: ""An error occurred: Import job failed: [{‘Arn’: ‘arn:aws:quicksight:eu-west-1:211125443023:datasource/ca62a712-3cc1-48e8-b4cb-da46f2ad28ba’, ‘Type’: ‘com.amazonaws.services.quicksight.model.InvalidParameterValueException’, ‘Message’: ‘Feature is not supported for this data source type’}]"
}
This is the datasource JSON as exported with “start_asset_bundle_export_job”:
Hello @kosta, upon first glance, I think the parameter that it is throwing an error on is the authenticationType param within the snowflakeParameters section. When looking through the boto3 documentation, it only shows 3 possible parameter options for snowflake:
Hello @kosta, okay, it at least seems like we are on the right track here. One thing I am curious about, are you using any kind of VPC to connect Snowflake to QuickSight? Maybe that is what we should be utilizing instead of the Credentials. Also, you may just need to add the Snowflake Parameters portion again within the Credentials parameter. This is how it looks in the documentation:
Hello @kosta, since we have not heard back from you, I will mark my previous response as the solution. Please let me know if you still need assistance with this issue and I can help guide you further. Thank you!
@kosta@DylanM My customer ran into the same “DataSourceCredentials field is incorrectly set” error, but with Redshift as the data source.
Kosta, are you still experiencing this issue? Thankfully we were able to identify the root cause and solve it. You may want to verify whether our error and solution are applicable to you.
First of all, we should’ve read the StartAssetBundleImportJob documentation carefully.
The documentation clearly states, the parameter override is intended for the data source included in the asset bundle
DataSources → (list)
A list of overrides for any DataSource resources that are present in the asset bundle that is imported.
Initially we used the target data source Id in our parameter override, which was incorrect. That was how we ran into the error. So the way we solved it by using the data source Id in the asset bundle (GUID) in our parameter override instead.