Open source · Python

Invictus-Nebius

Export audit events from Nebius tenants through the Nebius CLI. Pick the tenants and a time range; get every event in one JSON file.

License
MIT
Releases
None published · runs from main
Runs on
Python 3 · Nebius CLI
Cost
Free
SetupShell
# Sign in with the Nebius CLI (a named profile is optional)
nebius init --profile <your-profile-name>

# Run it, then choose tenants and a time range
python3 invictus-nebius.py --profile <your-profile-name>
✓ nebius_audit_export_<timestamp>.json
Works withNebiusNebius

What it does

Tenants in, one export out

Drives the Nebius CLI with the profile you already have. Every audit event in the range, for every tenant you choose.

SourcesOutputsInvictus-NebiusPython
Tenants
CLI profileaudit-event listOne JSON file · all tenantsYour SIEM or data lake

How it works

From sign-in to one export file

Everything after sign-in is prompted, so there is nothing to configure.

  1. 01

    Sign in

    Uses the session from nebius init, with the default profile or the one you pass with --profile.

  2. 02

    Choose tenants

    Lists the tenants the profile can see. Pick one by number, or all of them.

  3. 03

    Set the time range

    Start and end in ISO 8601 UTC. Leave them blank for the last 90 days.

  4. 04

    Export

    Follows page tokens until every event is retrieved, then writes one JSON file for all the tenants you chose.

What it runs

Two CLI calls, one file

The script drives the Nebius CLI; it calls no API of its own.

Read the README
StepWhatCommand
TenantsLists the tenants the profile can reachnebius iam tenant list
Audit eventsEvery event per tenant, in the chosen range, page by pagenebius audit v2 audit-event list
OutputOne JSON array of all events, written to the folder you run it fromnebius_audit_export_<timestamp>.json

Before you run it

Permissions, scope and clean-up

Access

Whatever the Nebius CLI profile can read. The script adds no credentials or permissions of its own.

Where output goes

The folder you run it from. The timestamp in the file name is local time; event times are as Nebius returns them.

Time range

The format is checked; the order is not. Make sure the start comes before the end.

No events

If the range returns nothing, no file is written. A failed CLI call stops the run.

Where it’s used

Where it fits

ServiceIncident response

Investigating activity in a Nebius tenant.

Open
ResearchIncident response in the neocloud

The blog series the script was written for.

Releases

No tagged releases yet

Recent commits

The repository has no published releases. Install from the main branch, and check the commit history for recent changes.

More tools

The rest of the toolkit

Invictus-Nebius

Got the export and need help reading it?

A responder can go through the events with you.