Docs

Volcano Engine Function as a Service

All-in-one sandbox

Deploying All-in-One Sandbox applications with a few clicks

This topic describes how to deploy an All-in-One Sandbox application with a few clicks by using the Application Center of Volcano Engine Function as a Service (veFaaS).

Background information

Application introduction

All-in-One Sandbox functions as a highly integrated, multifunctional environment for cloud-based development and execution. It is mainly used to encapsulate all essential tools required for a complete development and interaction process into a single sandbox. The tools include the browser, shell terminal, file system, VSCode editor, and Python/node.js code execution. This provides a standardized, ready-to-use environment for automated tasks (especially AI agents), cloud-based development, and secure code execution.

All-in-One Sandbox addresses the issues of traditional separated tool chains, such as environment inconsistency, cumbersome file transfers, and difficulty in add-on interaction, which delivers a truly integrated and seamless experience.

Runtime

Native runtime

Associated cloud services

warning

The fees for using associated cloud services will be incurred. For billing details, see the billing documentation of the associated cloud services.

veFaaS: veFaaS is used to create sandbox instances.

API Gateway (APIG): APIG is used to access services in All-in-One Sandbox.

Considerations

This feature is only supported in the China (Beijing) region.

Prerequisites

An APIG instance of the Serverless gateway type has been created. For detailed operations, see Creating instances.

If you use veFaaS for the first time, make sure that the cross-service authorization is complete. If the authorization is not complete, the cross-service authorization page will appear, which provides guidance on authorization.

Procedure

In the top navigation bar, select the target region.

In the left navigation bar, click App > App plaza.

On the App plaza page, select the All-in-One Sandbox template and click Create sandbox app.

On the Create sandbox app page, configure application parameters.

Parameter	Description
Basic information
Name	Specify a custom name for the sandbox application. The sandbox application name must be unique within the same account. The name cannot be modified after being created.
For sandbox images
Container image	The latest All-in-one sandbox image version is selected by default.
Gateway routing configuration
Domain type	Domain type of the sandbox application: Unified domain: All the instances in a sandbox application share the same domain name. You can target a specific instance by including the x-faas-instance-name header or the faasInstanceName query parameter in requests. Wildcard domain: [Beta - apply for trial] Each sandbox instance can have a separate access address. For description of sandbox instances, see Sandbox instances.
APIG instance	Select an APIG instance. The sandbox application will use an API gateway as the traffic entrance.
Gateway service	Select the service that corresponds to the APIG instance.
Route name	Specify a custom route name. The route name cannot be modified after being created.
Path	Set a request path through which the sandbox application can be accessed. It can be matched only by a prefix and must start with a forward slash (/).
Environment variables
Environment variables	Configure custom environment variables, which can be directly read during the runtime of the function code. tip If you set the Container image parameter to Custom images, veFaaS will automatically parse the configuration file of the target image to obtain the environment variables for the image. You can modify it if necessary.
Advanced settings	For details, see Function configuration.

Click Confirm to create and deploy the application.

You will be automatically redirected to the application details page, which displays the application deployment logs in real time.

Operation result

After the application is deployed, click the access address below the API gateway ID in the Linked cloud resource section on the application details page to go to the interactive interface of your application.

What to do next

Using All-in-One Sandbox

You can call All-in-One Sandbox by using an API, SDK, and MCP.

For API usage instructions, visit https://sandbox.agent-infra.com/api.

The sample Python SDK is as follows.

tip

In the sample code, $URL indicates the access endpoint of the sandbox. For the method of obtaining the endpoint, see Accessing sandbox instances.

from agent_sandbox import Sandbox

client = Sandbox(base_url="$URL")

ctx = client.sandbox.get_sandbox_context()
print(ctx)

result = client.shell.exec_command(command="ls -la")
print(result)

The MCP endpoint is /v1/mcp. You can append the MCP endpoint to the access address of the application to form the full MCP address, which is shown in the following example.

{
"mcpServers": {
"aio-sandbox": {
"url": "https://sd2mleni5ni4n75n9****.apigateway-cn-beijing.volceapi.com/v1/mcp"
}
}
}