CreateAgenticSpace - File Storage NAS - Alibaba Cloud Documentation Center

Creates an Agentic space.

Operation description

Before you begin

Before calling this operation, complete the following preparations:

An Agentic file system is created: When calling CreateFileSystem to create a file system, set the following parameters:
- FileSystemType: Set to standard.
- StorageType: Set to Agentic.
- ProtocolType: Set to NFS.
- Supported regions: The Agentic storage type is available only in specific regions and zones. Go to the NAS console to view the available regions and zones, or contact Alibaba Cloud technical support to obtain the latest list of supported regions.

Usage notes

This operation applies only to Agentic file systems.
Complete call chain example:
1. Call CreateFileSystem to create an Agentic file system (FileSystemType=standard, StorageType=Agentic, ProtocolType=NFS).
2. After the file system is created and its status changes to Running, call this CreateAgenticSpace operation to create an Agentic space.
3. To modify the configurations of the Agentic space, call the ModifyAgenticSpace operation.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

nas:CreateAgenticSpace

create

*Fileset

acs:nas:{#regionId}:{#accountId}:filesystem/{#filesystemId}

None

Request parameters

Parameter	Type	Required	Description	Example
FileSystemId	string	Yes	The ID of the file system.	31a8e4****
Azone	string	Yes	The zone ID.	cn-hangzhou-i
FileSystemPath	string	Yes	The absolute path of the file. Only first-level directories are supported.	/path/
Description	string	No	The description of the Agentic space. Limits: The description must be 2 to 128 characters in length. It must start with a letter or a Chinese character and cannot start with `http://` or `https://`. It can contain digits, colons (:), underscores (_), and hyphens (-).	AgenticSpace Description
Quota	object	Yes	The quota information.
FileCountLimit	integer	Yes	The maximum number of files allowed by the quota. Valid values: Minimum value: 10,000. Maximum value: 100,000,000.	10000
SizeLimit	integer	Yes	The total capacity limit of the quota. Unit: bytes. Valid values: Minimum value: 10,737,418,240 (10 GiB). Maximum value: 1,099,511,627,776,000 (1,024,000 GiB). Step: 1,073,741,824 (1 GiB).	10737418240
DryRun	boolean	No	Specifies whether to perform a dry run on the modification request. A dry run checks the validity of parameters and dependencies without actually modifying the instance or incurring fees. Valid values: true: sends a check request. The protocol service is not modified. The system checks whether required parameters are specified, the request format is valid, and business limits and dependencies are met. If the request fails the dry run, an error is returned. If the request passes the dry run, the HTTP status code 200 is returned. false (default): sends a normal request. If the request passes the dry run, the protocol service is directly modified.	false
ClientToken	string	No	The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, and you must make sure that the value is unique among different requests. The client token can contain only ASCII characters and cannot exceed 64 characters in length. For more information, see How to ensure idempotence. Note If you do not specify this parameter, the system automatically uses the RequestId of the API request as the ClientToken. The RequestId of each API request may be different.	123e4567-e89b-12d3-a456-42665544****

Response elements

Element	Type	Description	Example
	object
RequestId	string	The request ID.	98696EF0-1607-4E9D-B01D-F20930B6****
AgenticSpaceId	string	The ID of the Agentic space. After an Agentic space (an independent workspace allocated to a single agent end user in AgenticFS) is created, the system assigns this globally unique identifier to the space.	agentic-229oypxjgpau2****

Examples

Success response

JSON format

{
  "RequestId": "98696EF0-1607-4E9D-B01D-F20930B6****",
  "AgenticSpaceId": "agentic-229oypxjgpau2****"
}

Error codes

HTTP status code	Error code	Error message	Description
400	IllegalCharacters	The parameter contains illegal characters.	The parameter contains illegal characters.
400	MissingFileSystemId	FileSystemId is mandatory for this action.	The FileSystemId parameter is not specified.
400	MissingFileSystemPath	FileSystemPath is mandatory for this action.	The FileSystemPath parameter is missing.
400	InvalidFilesystemType.NotSupport	This Api does not support this fileSystem type.	The current interface does not support this type of file system.
400	InvalidFilesystemVersion.NotSupport	This Api does not support this fileSystem version.	This Api does not support this fileSystem version.
400	InvalidRequest	The request is invalid.	Invalid request
400	Quota.Invalid.Limit	Quota limit is invalid.	Invalid quota.
400	Resource.Exceed.Limit	Resource exceed limit.	The number of resources exceeds the limit.
400	Resource.Check.Fail	Resource check failed.	The resource check failed.
400	Fileset.Path.Duplicate	Fileset path is duplicate.	Fileset path is duplicate.
400	Fileset.Path.Nested	Fileset path is nested.	Fileset path is nested.
400	Fileset.Path.NotExist	Fileset.Path.Not.Exist.	Fileset parent directory path does not exist.
400	Fileset.Path.Exist	Fileset already exist.	Fileset path already exists.
403	OperationDenied.AlreadyExists	The operation is denied due to IdirName already exists in parent path.	The directory name to be created already exists in the parent directory.
403	OperationDenied.TooManyFilesets	The operation is denied due to too many fileset in filesystem.	The number of Fileset directories in the file system exceeds the threshold.
403	OperationDenied.TooManyDepths	The operation is denied due to Fileset path too deep.	The Fileset directory path depth exceeds the threshold.
403	OperationDenied.NestedDir	The operation is denied due to nested directory.	Failed to create the automatic update configuration because nested directories exist.
403	OperationDenied.DependencyViolation	The operation is denied due to dependancy violation.	The conditions for performing this operation are not met.
403	OperationDenied.FilesetNotSupported	The operation is not supported.	The file system does not support Fileset.
404	InvalidFileSystem.NotFound	The specified file system does not exist.	The specified file system does not exist.
404	InvalidFileSystemPath.ParentNotFound	The specified parent path does not exist.	The specified parent directory does not exist.
404	InvalidFileSystemPath.NotDirectory	The specified idir parent path is not directory.	The specified parent directory is not a directory.
404	InvalidFileSystemPath.InvalidCharacters	The specified fileset path contains invalid characters.	The specified Fileset path contains invalid characters.
404	InvalidFilesetPath.InvalidParameter	Fileset path is invalid.	The specified fileset path is invalid.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.