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 putsdcloudon your PATH and linksewsto it;ews upgradeon an older installation does the same.ews …runs exactly the same commands, so scripts and kubeconfig entries that runewskeep working. DCLOUD_*environment variables. The CLI readsDCLOUD_API_URL,DCLOUD_ACCESS_KEY,DCLOUD_PROFILE,DCLOUD_ORG,DCLOUD_REGIONand the rest first, and theEWS_*name of each when the new one is unset.~/.dcloud. On its first run the CLI moves~/.ewsto~/.dcloudand leaves~/.ewsas a link to it, so an older binary still finds your login. Where the move is not possible (a read-only home),~/.ewsis used as it is.- The API accepts the new forms beside the old ones:
Authorization: DCLOUD-ACCESS-KEY <id>:<secret>besideEWS-ACCESS-KEY;X-DCLOUD-RegionbesideX-EWS-Region; resource namesrn:dcloud:…besidern:ews:…in policies, trust policies, bucket policies, key scopes and role names; condition keysdcloud:SourceIpand the rest besideews:…; the bucket-policy principal{"DCLOUD": …}beside{"EWS": …}. - Deploy and CI accept the new forms:
dcloud-secret://NAMEbesideews-secret://NAMEin an imported.env;x-dcloud-release: truebesidex-ews-releasein a compose file; workflows in.dcloud/workflowsbeside.ews/workflows(a file in.dcloud/workflowswins over one of the same name in.ews/workflows);uses: dcloud/deploy@v1anddcloud/configure-credentials@v1beside theews/…names on Deutsche Cloud's runners. - Events: a rule written for
dcloud.<service>orDCLOUD API Callmatches the platform's events, and so does one written forews.<service>orEWS API Call. Event sources starting withdcloud.and metric namespaces starting withDCLOUD/are reserved for the platform. - MCP: tools are listed as
dcloud_<service>_<resource>_<operation>, and the connect snippets name the serverdcloud. 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), Pythondcloud-sdk(import dcloud) and Go packagedcloud. They readDCLOUD_*first andEWS_*after,~/.dcloud/credentials.jsonand else~/.ews/credentials.json;EwsClientand the otherEws*names stay as deprecated aliases. See SDKs. - Terraform: the provider is
dcloud(source = "<console host>/dcloud/dcloud", typesdcloud_*). Theewsprovider keeps being served, as before plus one warning, and amovedblock 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 asDCLOUD_*, and webhooks, event, schedule and audit deliveries carry everyX-EWS-*header also asX-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:orews: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, anews-sdk, theewsTerraform 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 --envand pooled apps:DCLOUD_REGIONandEWS_REGION,DCLOUD_RUN_IDandEWS_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-256andX-EWS-Signature-256, and so on. Event and schedule messages put on a queue carrydcloud-…andews-…attributes. - The CI secret
DCLOUD_BRANCH_DATABASE_URL, also asEWS_BRANCH_DATABASE_URL.
Reference
dcloud --versionprintsdcloud <version> (build …)whichever name started it.- At a terminal, the first command of a day that uses an old name (the
ewscommand, anEWS_*variable,~/.ews) prints one line on stderr saying so. In CI (CIset), when stderr is not a terminal, and with--jsonnothing is printed, so a script's output does not change. dcloud eks update-kubeconfigwrites new contexts asdcloud-<cluster>; a context written asews-<cluster>keeps working.
What is not supported yet
- API answers, events and audit records still show resource names as
rn:ews:…, and events asews.<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 theEWS-ACCESS-KEYscheme andX-EWS-Region. - The Go module path stays
github.com/deutschlandgpt/ews/sdk/go(the repository's path).
Troubleshooting
ews: command not foundafter a fresh install. The installer linksewsnext todcloud; if it could not (it says so), runln -s dcloud ~/.local/bin/ewsor usedcloud.- An older
ewsbinary says "not logged in". It reads~/.ews; check that~/.ewsis a link to~/.dcloud(ls -l ~/.ews). Runningdcloudonce creates it.