You know that moment when every data scientist asks for access and the DevOps team sighs? That’s the gap Domino Data Lab Eclipse was built to close. It turns the messy business of provisioning secure compute and data into a clean, auditable workflow that scales with real teams, not fantasy ones.
Domino Data Lab runs the show for enterprise data science platforms. Eclipse extends that power into the infrastructure layer, automating how projects connect to secure environments. Think of it as the identity interpreter between business policy and engineering reality. It synchronizes users, permissions, and environments so that the right people can launch reproducible analyses without pinging three different admins for keys.
Eclipse starts by mapping identity from your provider, often Okta or Azure AD, into Domino’s workspace logic. It uses standards like OIDC and SAML to federate access cleanly, then enforces compute boundaries using your existing AWS IAM or Kubernetes RBAC roles. The result is a single access model across every tool that touches sensitive data. No more brittle shell scripts trying to sync roles at 2 a.m.
In practice, the integration feels simple even when the back end is not. Once your identity is bound to Domino projects, Eclipse keeps the session active through secure tokens, logs each event for audit, and isolates containers per environment. The design is focused on repeatability. If an experiment worked last week, it will work again next week with the same permissions and compute footprint. For data science teams, that consistency is golden.
A quick rule worth following: always enforce least privilege within Eclipse’s project templates. Map roles to real personas, not blanket groups. Rotate credentials regularly, and log every environment handshake. The Domino API makes automation easy, but control still matters.