Call the CreateDeploymentSet operation to create a deployment set.

Usage notes

For the policies, precautions, and operation instructions of deployment sets, refer to Managing deployment sets.

Request description

When you call this operation, if you do not pass in optional parameters, the original configuration is retained.

Debugging

API Explorer

You can initiate calls online through API Explorer without paying attention to the signature generation process and quickly obtain the call results.

Go to debug

Request parameters

Only the request parameters specific to this operation and some common parameters are listed below. For more information, refer to Common parameters.

Action string required Sample value: CreateDeploymentSet

The action that you want to perform. Value: CreateDeploymentSet.

Version string required Sample value: 2020-04-01

The version of the API. Valid value: 2020-04-01.

ClientToken string Optional Sample value: 333456899ff****

The ClientToken is used to ensure the request idempotency. You can use the client to automatically generate a token, but you must make sure that the token is unique among different requests. This prevents repeated actions due to multiple client retries when the call of the API action times out or an internal server error occurs.

Value: Only ASCII characters are supported. The length is no more than 64 ASCII characters.

DeploymentSetName string required Sample value: testDeploymentSetName

The name of the deployment set.

Cannot start with a number, a hyphen (-), or an underscore (_).

Only Chinese characters, letters, numbers, underscores, and hyphens are allowed.

The length limit is 1 to 128 characters.

Description string Optional Sample value: testDescription

The description of the deployment set.

It must start with a letter or Chinese character.

Only Chinese characters, letters, numbers, dots (.), spaces, underscores (_), hyphen (-), equal signs (=), English comma (,), Chinese comma (，), and Chinese period (。) are allowed.

The length is limited to 255 characters.

tip

When an empty string is passed in, the existing description is cleared.

Granularity string Optional Sample value: host

The deployment granularity. Valid values:

host: physical machine

rack: rack

switch: switch

GroupCount integer Optional Sample value: 3

Set the number of availability groups.

Value range: 1–7.

Default value: 7

tip

When the value of Strategy is AvailabilityGroup, this parameter is required.

Strategy string Optional Sample value: Availability

The deployment policy. Valid values:

Availability (default): Availability policy.

AvailabilityGroup: Availability Group policy.

Response parameters

Only the response parameters specific to this operation are listed below. For more information, refer to the response structure.

DeploymentSetId string Sample value: dps-yc1o9aahks5m57nk****

The ID of the deployment set.

Sample request

Sample response

Error codes

The table below lists the business-related error codes of the operation. For more information, refer to Common error codes.

Status code	Error code	Error message	Description
400	IdempotentParameterMismatch	The request uses the same client token as a previous, but non-identical request. Do not reuse a client token with different requests, unless the requests are identical.	The idempotent parameters are inconsistent.
400	InvalidClientToken.Malformed	The specified ClientToken is malformed.	The specified ClientToken is invalid.
400	InvalidDeploymentSetDescription.Malformed	The specified deployment set description is malformed.	The specified deployment set description is invalid.
400	InvalidDeploymentSetGranularity.Malformed	The specified deployment set granularity is malformed.	The specified deployment set granularity is invalid.
400	InvalidDeploymentSetName.Malformed	The specified DeploymentSetName is malformed.	The specified deployment set name is invalid.
400	InvalidDeploymentSetStrategy.Malformed	The specified deployment set strategy is malformed.	The specified deployment set policy is invalid.
412	IdempotentProcessing	The request uses the same client token as a previous one that is still in process.	The previous idempotent request is still in process. Please try again later.
500	InternalError	An internal error has occurred.	An internal error occurred. Try again. If multiple attempts fail, submit a ticket.

Elastic Compute Service