Secure access authenticates communication between SDK and sandbox controller. Sandbox controller runs in sandbox itself and exposes APIs for work with file system, run command etc. Without using secured access, anyone with sandbox ID can access the controller APIs and control the sandbox from inside.Documentation Index
Fetch the complete documentation index at: https://e2b-mintlify-exclude-sandbox-template-from-search-79913.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
SDKs version
v2.0.0 and above are using secure access by default when creating sandbox. This may not be compatible with older custom templates and you may need to rebuild them.Migration path
When you are using custom templates created before envdv0.2.0, you need to rebuild the templates to enable secure access.
Temporary, you can disable secure access by setting secure to false during sandbox creation, but this is not recommended for production use as it opens up security risks.
You can check template envd version via e2b template list command or templates list in dashboard.
Supported versions
All sandboxes based on template with envd version at leastv0.2.0 already supports secure access without any additional changes.
Secured access flag was introduced in 1.5.0 for JavaScript and Python SDKs to be used optionally.
With SDKs version v2.0.0 and above, sandboxes are created with secure access enabled by default.
Access sandbox API directly
In some cases you may want to access sandbox controller APIs directly via its URL, for example when you are not using SDKs. When secure access is enabled, you need to provide an authentication token that was returned during sandbox creation. Each call to sandbox controller must include an additional headerX-Access-Token with access token value returned during sandbox creation.
For sandbox upload and download URLs, you need to generate pre-signed URLs. We are advising to use SDK for generating presigned URLs.