Secured access

Secure access provides authentication for communication between the SDK and the sandbox controller. The sandbox controller runs inside each sandbox, and it exposes the management interface used by the SDK, including file-system operations, command execution, and other sandbox control capabilities. When secure access is disabled, anyone with the sandbox ID can invoke these interfaces, which may allow unauthorized control of the sandbox from within the environment. Starting with SDK version v2.0.0, secure access is turned on automatically whenever a sandbox is created. Older custom templates might not support secure access, in which case a rebuild may be required.

Migration path

For custom templates created with envd earlier than v0.2.0, secure access is available only after the template is rebuilt. You can set secure to false to temporarily disable secure access during sandbox creation, but disabling secure access is not recommended for production use because of security risks. Use novita-sandbox-cli template list to check the template Envd version. You can also inspect templates in the dashboard.

Disable secure access

Disabling secure access is not recommended because it may expose the sandbox to security risks.

import { Novita } from 'novita-sandbox'

const novita = new Novita()
const sandbox = await novita.sandbox.create({ secure: false }) // Explicitly disable.

from novita_sandbox import Novita

novita = Novita()
sandbox = novita.sandbox.create(secure=False) # Explicitly disable.

Get started

Model APIs

Novita Sandbox

GPUs

Observability

Resources

Migration path

Disable secure access

​Migration path

​Disable secure access

Migration path

Disable secure access