You're staring at another approval queue, waiting for access to a production dataset that someone locked behind ten layers of policy. The clock ticks, your deploy window shrinks, and the Slack thread grows stale. Compass Eclipse exists to kill that wait time without killing your audit trail.
Compass Eclipse combines identity-driven access with intelligent session routing. Think of it like GPS for your cloud permissions. Compass handles authentication and organization-level identity. Eclipse focuses on runtime context, deciding which workloads or users get through and how their actions are logged. The pairing is simple but powerful, like matching AWS IAM with dynamic policy enforcement that never misses a beat.
When integrated, Compass Eclipse acts as an identity-aware proxy sitting between your developers and infrastructure. It checks tokens, verifies scopes, and maps user privileges directly to system actions. Instead of storing long-lived credentials, it issues ephemeral certificates or short JWTs that expire quickly. Most teams connect it with Okta or another OpenID Connect provider, then let Eclipse handle downstream policies using metadata and rules that travel with each request.
How do I connect Compass and Eclipse?
You link them through your identity provider. Compass defines who everyone is, Eclipse defines what they can touch and for how long. Set up an OIDC trust, point Eclipse at Compass’s identity endpoint, and configure a few scopes. The system will handle session validation automatically. That one connection turns messy permission sprawl into clean, traceable paths.
In daily operations, this means fewer manual tickets and less waiting for credentials. Developers can request and receive secure access instantly, with full audit visibility for compliance teams. If something misfires, logs reveal exactly which identity performed what action, when, and from where. SOC 2 checks go faster, incident response feels less like archaeology, and onboarding new engineers stops being a week-long scavenger hunt.