ews is now dcloud

The short name is dcloud: what changed, what to change, what keeps working.

Deutsche Cloud has one short technical name: dcloud. It is the command you type, the directory in your home, the prefix of the environment variables the tools read, and — step by step — the prefix of identifiers. The old short name ews keeps working until at least 31 December 2027 wherever it is read, and nothing you have today stops working.

Release note — 18 November 2026

  • The command line is dcloud. The installer puts dcloud on your PATH and links ews to it; ews upgrade on an older installation does the same. ews … runs exactly the same commands, so scripts and kubeconfig entries that run ews keep working.
  • DCLOUD_* environment variables. The CLI reads DCLOUD_API_URL, DCLOUD_ACCESS_KEY, DCLOUD_PROFILE, DCLOUD_ORG, DCLOUD_REGION and the rest first, and the EWS_* name of each when the new one is unset.
  • ~/.dcloud. On its first run the CLI moves ~/.ews to ~/.dcloud and leaves ~/.ews as a link to it, so an older binary still finds your login. Where the move is not possible (a read-only home), ~/.ews is used as it is.
  • The API accepts the new forms beside the old ones: Authorization: DCLOUD-ACCESS-KEY <id>:<secret> beside EWS-ACCESS-KEY; X-DCLOUD-Region beside X-EWS-Region; resource names rn:dcloud:… beside rn:ews:… in policies, trust policies, bucket policies, key scopes and role names; condition keys dcloud:SourceIp and the rest beside ews:…; the bucket-policy principal {"DCLOUD": …} beside {"EWS": …}.
  • Deploy and CI accept the new forms: dcloud-secret://NAME beside ews-secret://NAME in an imported .env; x-dcloud-release: true beside x-ews-release in a compose file; workflows in .dcloud/workflows beside .ews/workflows (a file in .dcloud/workflows wins over one of the same name in .ews/workflows); uses: dcloud/deploy@v1 and dcloud/configure-credentials@v1 beside the ews/… names on Deutsche Cloud's runners.
  • Events: a rule written for dcloud.<service> or DCLOUD API Call matches the platform's events, and so does one written for ews.<service> or EWS API Call. Event sources starting with dcloud. and metric namespaces starting with DCLOUD/ are reserved for the platform.
  • MCP: tools are listed as dcloud_<service>_<resource>_<operation>, and the connect snippets name the server dcloud. A tool's old name, ews_<service>_…, still works when called: it is no longer listed, so the tool list does not double. An agent that only runs tools it was allowed by name (Claude Code --allowedTools mcp__ews__ews_…, per-tool approvals) needs the new names in that list.
  • SDKs: @dcloud/sdk (DcloudClient), Python dcloud-sdk (import dcloud) and Go package dcloud. They read DCLOUD_* first and EWS_* after, ~/.dcloud/credentials.json and else ~/.ews/credentials.json; EwsClient and the other Ews* names stay as deprecated aliases. See SDKs.
  • Terraform: the provider is dcloud (source = "<console host>/dcloud/dcloud", types dcloud_*). The ews provider keeps being served, as before plus one warning, and a moved block per resource takes existing state over without replacing anything. See Terraform.
  • Both names on what the platform sends: functions, CI jobs, pods with a pod identity and pooled apps get every EWS_* variable also as DCLOUD_*, and webhooks, event, schedule and audit deliveries carry every X-EWS-* header also as X-DCLOUD-* (below, "What keeps working").

What to change, and when

Nothing has to change now. To move to the new names at your own pace:

You use Change it to
the ews command in scripts dcloud
EWS_API_URL, EWS_ACCESS_KEY, … for the CLI or SDKs DCLOUD_API_URL, DCLOUD_ACCESS_KEY, …
EwsClient, ews_sdk, Go package ews DcloudClient (@dcloud/sdk), dcloud, Go dcloud
Authorization: EWS-ACCESS-KEY … in your own requests Authorization: DCLOUD-ACCESS-KEY …
X-EWS-Region X-DCLOUD-Region
rn:ews:… in a policy you write rn:dcloud:… (both match the same resources)
ews:SourceIp and the other condition keys dcloud:SourceIp, …
{"EWS": …} in a bucket policy {"DCLOUD": …}
ews-secret://NAME in an .env you import dcloud-secret://NAME
x-ews-release: true in a compose file x-dcloud-release: true
.ews/workflows/ .dcloud/workflows/
uses: ews/deploy@v1, ews/configure-credentials@v1 uses: dcloud/deploy@v1, dcloud/configure-credentials@v1
Terraform source = "<host>/ews/ews", ews_* types <host>/dcloud/dcloud, dcloud_*, with moved blocks (Terraform)

A policy, trust policy or bucket policy you saved keeps the text you wrote: Deutsche Cloud never rewrites it, and rn:ews:… and rn:dcloud:… mean the same resource in every comparison — an Allow and a Deny alike.

What keeps working

Every access key, git token, OAuth grant and SCIM token issued so far stays valid until it expires or you revoke it. The old names are read until at least 31 December 2027, and they are turned off only once nobody uses them.

IAM → Old names in use (/iam/old-names) shows what in your organization still uses them:

  • custom policies and role trust policies written with rn:ews: or ews: condition keys;
  • AI agents that call MCP tools by their old ews_… names, with who and when;
  • access keys used by a tool built before the rename (ews-cli, an ews-sdk, the ews Terraform provider).

An API request that uses the EWS-ACCESS-KEY scheme or the X-EWS-Region header is served as before, and its answer carries Deprecation, Sunset: Fri, 31 Dec 2027 23:59:59 GMT and Link: </docs/dcloud-rename>; rel="deprecation". An MCP tool called by its old name answers with _meta.deprecated, which names the tool to use instead. (The current dcloud and SDKs still send EWS-ACCESS-KEY themselves; they switch with the new key format, and nothing needs doing for them.)

What the platform hands your code comes under both names, with the same value:

  • Environment variables in functions, CI jobs, pods with a pod identity, ews-instance credentials --env and pooled apps: DCLOUD_REGION and EWS_REGION, DCLOUD_RUN_ID and EWS_RUN_ID, and so on. A variable your job sets itself wins, name by name.
  • Headers on event, schedule, git webhook, audit webhook and queue-trigger deliveries: X-DCLOUD-Signature-256 and X-EWS-Signature-256, and so on. Event and schedule messages put on a queue carry dcloud-… and ews-… attributes.
  • The CI secret DCLOUD_BRANCH_DATABASE_URL, also as EWS_BRANCH_DATABASE_URL.

Reference

  • dcloud --version prints dcloud <version> (build …) whichever name started it.
  • At a terminal, the first command of a day that uses an old name (the ews command, an EWS_* variable, ~/.ews) prints one line on stderr saying so. In CI (CI set), when stderr is not a terminal, and with --json nothing is printed, so a script's output does not change.
  • dcloud eks update-kubeconfig writes new contexts as dcloud-<cluster>; a context written as ews-<cluster> keeps working.

What is not supported yet

  • API answers, events and audit records still show resource names as rn:ews:…, and events as ews.<service> / EWS API Call.
  • Metric namespaces are still EWS/<namespace>.
  • New access keys still start with EWS1, and the CLI and the SDKs still send the EWS-ACCESS-KEY scheme and X-EWS-Region.
  • The Go module path stays github.com/deutschlandgpt/ews/sdk/go (the repository's path).

Troubleshooting

  • ews: command not found after a fresh install. The installer links ews next to dcloud; if it could not (it says so), run ln -s dcloud ~/.local/bin/ews or use dcloud.
  • An older ews binary says "not logged in". It reads ~/.ews; check that ~/.ews is a link to ~/.dcloud (ls -l ~/.ews). Running dcloud once creates it.
Did this page help you?