Skip to main content
Alibaba Cloud Agent Sandbox (Flash Edition) is a managed code-execution sandbox service that exposes an E2B-SDK-compatible API for creating, running commands in, listing and killing sandboxes. The following table shows what CostGraph runs on this provider.

​
Connect

Connect Alibaba Cloud Agent Sandbox on Integrations, and CostGraph starts sandboxes in your Alibaba Cloud Agent Sandbox account. You don’t run anything yourself.
  1. In CostGraph, go to Integrations > Sandbox > Alibaba Cloud Agent Sandbox.
  2. Enter these fields:
    • API key (ALIBABA_SANDBOX_API_KEY, required): An Agent Sandbox API key from the Agent Sandbox console.
    • Region (ALIBABA_SANDBOX_REGION, required): The region Agent Sandbox is deployed in, for example cn-hangzhou.
  3. Click Connect.

​
Your own dispatcher

To keep the key out of CostGraph or reach a private network, run your own dispatcher instead. Set provider to alibaba and the preceding fields as environment variables, as described in Run your own dispatcher. To see what Alibaba Cloud Agent Sandbox costs, connect the Alibaba Cloud Agent Sandbox integration.

​
Key and permissions

ALIBABA_SANDBOX_API_KEY is an Agent Sandbox Flash Edition API key, created in the Agent Sandbox console under Speed Edition > API Keys > Create an API Key (shown once; requires Function Compute and Agent Sandbox Flash Edition to be activated). ALIBABA_SANDBOX_REGION is the region where Flash Edition is deployed (cn-beijing, cn-shanghai, cn-hangzhou, cn-shenzhen, cn-hongkong, ap-southeast-1, us-east-1, us-west-1); it builds https://api.<region>.sandbox.aliyuncs.com. Not documented. The key-creation page lists no scopes or per-key permissions; it only says the account or RAM user creating the key needs permission to manage Flash Edition API keys (no RAM action named). Sources: www.alibabacloud.com: create api key, www.alibabacloud.com: e2b sdk compatible api list, www.alibabacloud.com: e2b sdk integration parameter description, www.alibabacloud.com: lifecycle.

​
Limits

  • Sandbox timeout set via setTimeout cannot exceed 86400 seconds (24 hours). (source)
  • Pause and resume is available only to allowlisted accounts. (source)
  • Snapshots and the Volume API are not supported through the E2B compatibility layer; capabilities depend on account quotas and region availability. CPU/memory caps, architecture and preview status are not documented. (source)
  • Key, API URL, domain, template and sandbox must all be in the same account and region or auth/creation fails. (source)