ec2.volumes.attachAttach a volume to an instance in the same region
POST /ec2/api/volumes/{id}/attachIAM ec2:AttachVolumeChanges state
Request syntax
POST /ec2/api/volumes/{id}/attach
{
"instanceId": "string"
}Path parameters
idRequiredstring
Constraints: /^vol-[0-9a-f]{6,32}$/
Request body
instanceIdRequiredstring
The instance to attach to (i-…), in the volume’s zone and not terminated
Constraints: /^i-[0-9a-f]{6,32}$/
Response
200: `data` is the volume, now `in-use`, with its instanceId and deviceName.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow ec2:AttachVolume on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud ec2 volumes attach id --instance-id examplecurl -X POST "https://console.platform-development.deutschecloud.app/ec2/api/volumes/id/attach" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"instanceId":"example"}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ec2_volumes_attach.