Storage API Access#

Note

Internal NVIDIA use only. These steps are for NVIDIA employees accessing internal Arena assets. Public S3 assets do not require login. Use omni.client 2.74.0 or newer.

1. Request write access (optional)#

This step is only needed to upload or modify assets in the Arena folder. Join the access-isaac-dev-storage-arena-write group on DLRequest.

2. Sign in and verify access#

Run the setup script from the repository root in your installed Arena runtime. It preserves existing credentials, starts NVIDIA device login only when credentials are missing, then lists the Arena storage root and reports whether you have write access.

The script implements the device-code flow from the Storage API authentication instructions and the credential-file setup from the login quickstart.

Native uv

uv run python tools/internal/setup_storage_access.py

Docker

Before creating the container, run from the repository root on the host:

mkdir -p "$HOME/.nvidia-omniverse"
unset OMNI_PASS
./docker/run_docker.sh

With OMNI_PASS unset, the launcher bind-mounts the existing host ~/.nvidia-omniverse directory into the container.

Inside the container, run as your normal host user:

python tools/internal/setup_storage_access.py

The script writes config/auth.toml through the mount to the host. Credentials survive container removal and are reused by new containers launched with the same ~/.nvidia-omniverse directory mount.

When prompted, open https://login.microsoft.com/device in a browser, enter the code printed by the script, and complete your NVIDIA sign-in.

This allows you to read and upload assets to the Arena folder in the Storage API. See Assets Management for the asset upload and release workflow.

Credentials are saved at ~/.nvidia-omniverse/config/auth.toml. omni.client refreshes access tokens automatically.

For renewing an existing login, follow the internal device-login guide. For unattended CI, use the Storage API federation guide.