To migrate servers as a group, you must first associate the migration sources with that group.
Operation description
A migration source can be associated with only one group.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
smc:AssociateSourceServers |
update |
*All Resource
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| WorkgroupId |
string |
Yes |
The ID of the group. |
w-*** |
| SourceId |
array |
Yes |
The IDs of the migration sources. You can associate a maximum of 50 migration sources with a group. |
|
|
string |
No |
The ID of the migration source. |
s-bp1e2fsl57knvuug**** |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
The response parameters. |
||
| RequestId |
string |
The request ID. |
C8B26B44-0189-443E-9816-D951F59623A9 |
Examples
Success response
JSON format
{
"RequestId": "C8B26B44-0189-443E-9816-D951F59623A9"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 500 | InternalError | An error occurred while processing your request. Please try again. If the problem still exists, please submit a ticket. | An error occurred while processing your request. Please try again. If the problem still exists, please submit a ticket. |
| 403 | Forbidden.Unauthorized | A required authorization for the specified action is not supplied. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.