Skip to content
Connection Guide

Connect GitHub Enterprise Server Without Breaking the Audit Trail

Use this guide to connect GitHub Enterprise Server or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategorySource control
Checklist3 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect GitHub Enterprise Server and make sure the first collection lands cleanly.

  1. 1
    Determine the GHES appliance API root (for example `https://ghes.example.com/api/v3`) and the target organization slug.
  2. 2
    Prefer GitHub App installation auth when the appliance version supports it; otherwise use a fine-grained PAT with equivalent read-only scope.
  3. 3
    Validate repo inventory, code-scanning alerts, and organization audit-log collection before enabling scheduled sync.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

private_key_pemaccess_token

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.