Skip to main content

Connect to external data sources

This article explains how to connect your SAP Databricks workspace to non-SAP data sources.

SAP Databricks supports reading data from some cloud storage buckets, external APIs, and OpenSharing shares

Connect to an S3 bucket

Admins in SAP Databricks accounts deployed on AWS can create external locations to connect their workspace to an AWS S3 bucket. For instructions on connecting to an AWS S3 bucket, see Connect to an S3 bucket.

note

To prevent data loss, SAP Databricks requires that external locations be read-only.

Connect to a Azure blob storage location

Admins in SAP Databricks accounts deployed on Azure can create external locations to connect their workspace to an Azure blob storage location. For instructions on connecting to an Azure blob storage location, see Connect to Azure Data Lake Storage.

note

To prevent data loss, SAP Databricks requires that external locations be read-only.

Connect to a GCS bucket

Admins in SAP Databricks accounts deployed on GCP can create external locations to connect their workspace to a Google Cloud Storage (GCS) bucket location. For instructions on connecting to a GCS bucket, see Connect to a Google Cloud Storage bucket.

note

To prevent data loss, SAP Databricks requires that external locations be read-only.

Receive an OpenSharing share

SAP Databricks accounts can receive OpenSharing shares from workspaces both inside and outside their account. To learn about receiving and reading shared data, see Access data shared with you using OpenSharing.

note

SAP Databricks accounts can be the recipients of OpenSharing shares, but cannot initiate shares to locations outside of SAP.