ec2.instances.connect-status

Deutsche Cloud Connect on this instance: connected or not, who can log in, the keys Deutsche Cloud added

GET /ec2/api/instances/{id}/connectIAM ec2:DescribeInstancesRead

`state`: connected, pending (booting), disconnected (down, or `systemctl disable ews-connect` on the machine), off (launched with connect: false), not-installed (launched before Connect). `enableCommand` turns it on from the machine.

Request syntax

GET /ec2/api/instances/{id}/connect

Path parameters

  • idRequired

    string

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

Response

200: `data` is the status (`state`, `message`, `connectedSince`, `lastSeenAt`, `loginUsers`, `defaultUser`, `sshVersion`, `tunnelFingerprint`, `enableCommand`) and `keys`: the key pairs added through Connect, each with keyPairId, keyPairName, fingerprint, users and status.

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:DescribeInstances 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 connect-status id

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