🔌Integration with existing storage systems

Your Private Ellipsis Drive Instance can connect to existing storage systems and data sources. These connections are represented in Ellipsis Drive as synced folders, where external content is exposed as subfolders, layers, and files.

Synced folders reflect the state of the underlying storage system. When data is added, updated, or removed in the original storage, these changes are reflected in Ellipsis Drive once the synced folder is updated.

Synced folders are read-only within Ellipsis Drive. The structure and content remain governed by the connected storage system. This means that data within synced folders cannot be modified directly via the Ellipsis Drive API or interface. This preserves the integrity of the connected storage system and ensures alignment between the mounted external storage and its representation in Ellipsis Drive.

Synced folders are kept aligned with updates in the underlying storage system and are organized into an Ellipsis Drive-native structure of folders, layers, and timestamps.

Users can select spatial data from this structure for activation, after which it is published as web services for downstream use.

In cases where vector data is published as an editable service, modifications are applied to the Ellipsis Drive-managed representation within analytical workflows. Any edits result in new versions being created within Ellipsis Drive, while the original data in external storage remains unchanged.

The following storage systems can be connected as synced folders:

• Cloud buckets

• PostgreSQL tables

• MySQL tables

• BigQuery tables

• PostGIS tables

• File server disks

Storage systems can be connected via the Ellipsis Drive interface by providing the appropriate connection details. Credentials are managed at the account level via Manage account → external connection keys. From there, you can add a new key, select the storage type, and follow the setup wizard for configuration.