ec2.instances.attach-session

A fresh ticket to re-attach to your own session (the shell waits 60 s after a drop)

POST /ec2/api/instances/{id}/sessions/{sessionId}/attachIAM ec2:StartSessionChanges state

Request syntax

POST /ec2/api/instances/{id}/sessions/{sessionId}/attach

Path parameters

  • idRequired

    string

    Constraints: /^i-[0-9a-f]{6,32}$/

  • sessionIdRequired

    string

    Constraints: /^ses-[0-9a-f]{16}$/

Response

200: `data` holds a fresh single-use `ticket`, `expiresAt`, `websocketUrl` and the `session` record.

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:StartSession 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 instances attach-session id sessionId

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ec2_instances_attach-session.