Call the RedeployDedicatedHost operation to perform a full migration for a DDH.

Usage notes

When a DDH is in the UnderAssessment (potential risk) or TempUnavailable (temporarily unavailable) state, we recommend that you call this operation to initiate a failure-avoidance migration for it. This helps prevent permanent DDH failure. You can call the DescribeDedicatedHosts operation to view the DDH status.

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

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

Version string required Sample value: 2020-04-01

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

ClientToken string Optional Sample value: 23fa21A8823nfasd7f****

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 operation times out or an internal server error occurs.

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

DedicatedHostId string required Sample value: dh-3tigy72q3u3vj0x2****

The source dedicated host ID.

Response parameters

This operation has no specific response parameters. For more information, refer to Response structure.

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	InvalidDedicatedHost	The specified dedicated host does not support this request.	The current DDH does not support this operation.
400	InvalidDedicatedHostForMigrate.Unsupported	The specified dedicated host does not support migrate.	The specified dedicated physical machine does not support migration.
400	InvalidDedicatedHostStatus.Unsupported	The status of the specified dedicated host does not support this request.	The dedicated host in current status does not support this action.
400	InvalidInstanceStatus	The status of the specified instance does not support this request.	The current status of the instance does not support this operation.
400	MissingParameter.DedicatedHostId	The required parameter DedicatedHostId is not supplied.	The parameter DedicatedHostId cannot be empty.
404	InvalidDedicatedHost.NotFound	The specified dedicated host does not exist.	The specified dedicated host does not exist.
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	Insufficient.DedicatedHostCapacity	There is not enough capacity to fulfill your request.	The resources are currently insufficient. Try again later or select other dedicated host types.
500	InternalError	An internal error has occurred.	An internal error occurred. Try again. If multiple attempts fail, submit a ticket.

Elastic Compute Service