data_admin role or higher, and creating a new engine can also be gated by plan — see Entitlements.
The form
The Create query engine dialog opens with working defaults: the nametrino-default, the
trino kind and your tenant’s default data plane. Click Create and you have an engine. Everything
else sits under Advanced, which starts collapsed and opens on its own if one of its fields needs
fixing.
Catalogs aren’t configured here: an engine’s catalogs come automatically from your
federation-capable integrations on the same plane.
1
Name it and choose a plane
Pick the data plane the engine should run on. If you only have one plane, it’s already selected.
2
Pick a size (optional)
Open Advanced only if you want a size other than the default:
s if your plan allows it, the
platform’s baseline. See
Sizes and plans for what each rung sets and which ones your plan
includes.3
Choose an idle policy (optional)
Leave it at Platform default unless you have a reason to keep the engine running around the
clock (Never suspends) or to suspend it sooner than the default.
4
Create
The engine provisions, then its first catalog set is applied automatically — the apply runs after the
cluster exists, so there’s nothing running yet for it to interrupt and no failure to see. The engine
stays parked (Parked — wakes on first query) until you query it; it doesn’t boot a cluster nobody
has used yet. See Power and scale to zero.
What you get
Once created, the engine’s endpoint appears on its detail page and in the Connect dialog once provisioning publishes it —https://<engine-id>.engine.<plane-domain>, built from the engine’s own id so a later rename never
changes it. It authenticates as a confidential OAuth client of your tenant: signing in with
trino --external-authentication (or any OAuth2-aware Trino client) sends you to your tenant to
sign in, and the coordinator keeps your session alive from then on. See
Connect to an engine and Engine sign-in and OAuth.
From the CLI
Create an engine
dip engine create --name N [--plane P] [--kind trino] [--set size=xs|s|m|l|xl] [--set k=v]… [--idle-timeout SECONDS] — see the full flag reference at dip CLI commands.
If it’s refused
Related
Sizes and plans
What each rung of the size ladder sets, and which ones your plan allows.
Engine sign-in and OAuth
How a person and a machine each authenticate to an engine.