Create a directory in a file system using the CreateDir API - File Storage NAS - Alibaba Cloud - File Storage NAS

Operation description

Only the General-purpose NAS NFS file system supports this feature.

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:CreateDir

create

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
FileSystemId	string	Yes	The ID of the file system.	31a8e4****
RootDirectory	string	Yes	The name of the directory. The name must start with a forward slash (/). The name can contain digits and letters. The name can contain underscores (_), hyphens (-), and periods (.). The path cannot contain symbolic links, such as the current directory (.), the parent directory (..), or other symbolic links. Note If the root directory does not exist, you must configure the automatic creation information. The system automatically creates the specified root directory based on the settings. If the root directory already exists, you do not need to configure the automatic creation information. If you configure it, the configuration is ignored.	/test
OwnerUserId	integer	Yes	The ID of the user that owns the directory. Valid values: 0 to 4294967295.	1
OwnerGroupId	integer	Yes	The ID of the user group that owns the directory. Valid values: 0 to 4294967295.	123
Permission	string	Yes	Specifies the POSIX permissions applied to the root directory path. The value must be a valid octal number, such as 0755.	0755
Recursion	boolean	No	Specifies whether to create multi-level directories. Valid values: true (default): If the multi-level directories do not exist, the system creates them level by level. false: The system creates only the last-level directory. If the parent directory does not exist, an error message is returned.	true

Response elements

Element	Type	Description	Example
	object	Schema of Response
RequestId	string	The ID of the request.	BC7C825C-5F65-4B56-BEF6-98C56C7C****

Examples

Success response

JSON format

{
  "RequestId": "BC7C825C-5F65-4B56-BEF6-98C56C7C****"
}

Error codes

HTTP status code	Error code	Error message	Description
403	InvalidProtocolType.NotSupported	The specified protocol type does not supported.	The specified protocol type is not supported.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.