Domino Data Connectivity

by dominodatalabd86698d74d56No license7 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 2 days ago

Connect Domino workloads to external data sources including AWS S3 (via Mountpoint CSI driver), credential propagation with AWS IRSA and Azure Entra ID, and External Data Volumes. Use when configuring S3 access, setting up credential propagation, or connecting to cloud data sources from Domino.

Instructions onlyDevOps & Cloud
AI-generated overview

Guides connecting Domino workloads to external cloud data via S3 Mountpoint, AWS IRSA and Azure Entra ID credentials.

What it does
This skill supplies reference guidance for connecting Domino workloads to external data sources. It covers data access options such as datasets, data sources, External Data Volumes, S3 Mountpoint and credential propagation, and explains when to choose each. It also points to companion documents on S3 Mountpoint, AWS IRSA and Azure Entra ID, with short code examples for reading S3 data, using IRSA credentials and reading external volumes.
When to use it
Use it when configuring S3 access from Domino, setting up credential propagation, or connecting Domino workloads to cloud data sources. It is aimed at situations involving AWS S3, Azure storage, IRSA or Azure Entra ID integration.
Requirements
Instructions only; no scripts are shipped. It assumes a Domino environment with the relevant connectivity configured, such as Mountpoint S3, AWS IRSA or Azure Entra ID, and references Python libraries (pandas, boto3) in its examples.

Domino Data Connectivity Skill

This skill provides comprehensive knowledge for connecting Domino workloads to external data sources, including AWS S3, Azure storage, and credential propagation.

Key Concepts

Data Access Options in Domino

OptionUse Case
DatasetsProject-level data storage
Data SourcesExternal database connections
External Data Volumes (EDV)Mount external storage as volumes
S3 MountpointDirect S3 access as file system
Credential PropagationPass user identity to cloud services

Credential Propagation Methods

MethodCloudDescription
IRSAAWSIAM Role for Service Accounts via OIDC
Azure Entra IDAzureUser-based credential propagation

Related Documentation

  • S3-MOUNTPOINT.md - AWS S3 as local file system
  • AWS-IRSA.md - AWS IAM Role for Service Accounts
  • AZURE-CREDENTIALS.md - Azure Entra ID integration

Quick Start

Accessing S3 Data

With Mountpoint S3 configured, access S3 as a local file system:

python
import pandas as pd
# S3 data appears as local filesdf = pd.read_parquet("/mnt/s3-data/datasets/sales.parquet")

Using IRSA for AWS Services

With IRSA configured, AWS SDK uses automatic credentials:

python
import boto3
# No explicit credentials needed - IRSA provides thems3 = boto3.client('s3')response = s3.list_objects_v2(Bucket='my-bucket')

Accessing External Data Volumes

EDVs are mounted at configured paths:

python
# Read from external volumewith open("/mnt/external-data/config.json") as f:    config = json.load(f)

When to Use Each Option

Use S3 Mountpoint When:

  • Working with large datasets stored in S3
  • Need file system interface to S3
  • Want to avoid EFS costs for large data
  • Require multi-region data access

Use IRSA When:

  • Need AWS service access from Domino workloads
  • Policy prohibits long-lived credentials
  • Require user-level audit trails
  • Need cross-account role assumption

Use Azure Entra When:

  • Working with Azure data services
  • Need OAuth-based authentication
  • Require user-level access control
  • Need centralized RBAC

Blueprint References

GitHub Repository

Implementation templates available at: https://github.com/dominodatalab/domino-blueprints

Source and attribution

Source:dominodatalab/domino-claude-plugininskills/data-connectivityat commitd86698d

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal