cancel
Showing results for 
Search instead for 
Did you mean: 

DI_DATA_LAKE connection created wrongly in instance creation as S3 when hosting on GCP

0 Kudos

Dear all,

The instance created on GCP created two storages (1) CLOUD_STORAGE with description Google Cloud Storage and it woks fine. But the (2) DI_DATA_LAKE where the artefact producer stores model.

I noticed the DI_DATA_LAKE was created as S3 connected after installation so I changed to GCP and uploaded JSON key file for my service account, but no luck. It didn't work.

di-data-lake-conection-issue.jpg

As the python produce pipeline stores the model artefact in DI_DATA_LAKE, I am not able to progress my first pipeline... 😞

di-data-lake-conection-issue-in-artifact-producer.jpg

Is there a workaround or will SAP look at this issue as the connection created during instance creation points to S3 as in the screen shot attached?

kind regards,

Chitra T.

former_member255270
Active Participant
0 Kudos

Hi Chitra, please see my response here: https://answers.sap.com/answers/13209197/view.html

Accepted Solutions (0)

Answers (0)