Provider credentials & regions

Dedicated plans build a VPS through ImpulseCore’s provider integrations. Configure at least one provider and one region, set your DNS and TLS base, and pick the runtime defaults baked into new servers.

1. Add provider credentials

Open Settings → Providers & Regions. Enter API credentials for the VPS providers you intend to use — or leave a provider’s token blank to use the one saved in ImpulseCore → Operations → VPS Providers. The authoritative provider list, region maps, and default sizes come from ImpulseCore’s shared provider catalog — so when Core adds a provider, it becomes selectable here without a module update.

Provider	Example region	Example size
Vultr	dfw	vc2-2c-4gb
Hetzner Cloud	fsn1	cx22
DigitalOcean	nyc1	s-2vcpu-4gb
Linode (Akamai)	us-east	g6-standard-2
Amazon Web Services (EC2)	us-east-1	t3.medium
Microsoft Azure	eastus	Standard_B2s
Google Cloud (Compute Engine)	us-central1	e2-small
Proxmox VE	operator-defined	operator-defined

Test all configured providers on the same tab checks each saved account.

No SSH needed to verify

The Diagnostics → Health Checks → VPS Providers check confirms every configured provider API responds without provisioning anything.

2. Define regions

Still under Settings → Providers & Regions, define one or more regions. A region ties together:

• a customer-facing name and slug,
• a provider,
• a provider region code (for example dfw or fsn1),
• a default VPS plan,
• and, optionally, a per-region S3 snapshot bucket.

Region requests are a hard placement constraint

If a customer’s order explicitly names a region with no configured provider region code (or, for shared plans, no available capacity there), provisioning returns a specific no-capacity error rather than silently placing the instance elsewhere.

3. Configure DNS & TLS

Instances are addressed by hostname and served over TLS. Under Settings → DNS & TLS, configure:

• Service base domain — the domain new Valkey hostnames are built under (for example cache.example.com). Each dedicated service gets the hostname vk-<service id>.<base domain>; dedicated provisioning refuses to start until it is set.
• Cloudflare Zone ID / API token — optional. When set, the module creates the DNS records for new servers automatically. The token needs Zone:DNS:Edit and Zone:Zone:Read on that zone; Test DNS creates and deletes a TXT record to prove it.
• ACME registration email — reserved for public-certificate reissue. Valkey servers don’t request public certificates in this release: the Valkey port uses a self-signed certificate (see Connecting a cache client).
• Valkey TLS port — the exposed TLS listener port on dedicated servers (default 6380). Shared-plan tenants each get their own port on the pool box.
• Admin Proxy port — default 9099. WHMCS always reaches the scoped Admin Proxy over HTTPS on port 9098; the 9099 listener is a transitional plain-HTTP port that WHMCS doesn’t use. The server firewall opens both only to this WHMCS server’s IPs.

The Diagnostics → Health Checks → DNS & TLS Settings test verifies these values (base domain, Cloudflare token, zone id, ACME inputs, exposed TLS port) without provisioning anything.

4. Set runtime defaults

Under Settings → Runtime & Cache, review the defaults written into the bootstrap payload when a dedicated server is provisioned:

Setting	What it controls
Default VPS provider	Pre-selected for new regions and for orders with no region override.
Default region	Used when a product or service does not select a specific region.
Eviction policy	Default Valkey eviction policy applied at bootstrap and config-apply time (default allkeys-lru).
Default Valkey version	The pinned engine release new servers install from the official tarball (default 8.1.8; 9.1.0 is also available).
Password rotation grace	Minutes a previous password stays valid after a rotation (default 30).
Default OS image	Fallback Ubuntu 24.04 image slug when a provider-specific OS id is not set.

Defaults apply to new builds only

Existing servers keep their current settings until a config apply or package change updates them. Changing the default engine version pins new or rebuilt servers only — existing servers are moved with the in-place engine-upgrade flow, not by editing the setting.

5. Register shared pool boxes & existing hosts

Shared plans and bring-your-own boxes need a registered server before you can sell against them. Set WHMCS Server IPv4 (and IPv6, if this WHMCS server has one) under Settings → General & Access first — it is baked into each server’s firewall allowlist for the Admin Proxy.

Shared pool boxes

Shared plans place a per-tenant valkey@svc_N instance on an operator-run pool box. Before selling a shared plan, provision at least one shared pool server under Infrastructure → + Provision New Server (it needs a region and a configured provider, and sets the box’s Max tenants) so placement has capacity — otherwise shared placement returns a clear no capacity error when WHMCS runs the module’s Create, rather than provisioning.

Register a host you already own

Under Infrastructure → + Add Existing Server you can set up a Valkey server on a box you already own or manage — any provider, or bare metal, for a dedicated service or as a shared pool box. The module builds a one-time installer script:

1. Enter the host’s resolvable FQDN (point an A/AAAA record at it first) and any explicit IP.
2. Click Register host & build installer. The module creates the server record and a single-use token, which expires about two hours after you generate the installer.
3. Download the installer, save it on the host, and run it as root:

sudo bash install.sh

The installer pulls the server password, Admin Proxy secret, and allowlist over the single-use token, installs Valkey and the scoped Admin Proxy, and brings the server online — identical to a server the module provisions itself. Use Test Admin Proxy to confirm the Admin Proxy answers.

Nothing sensitive lives in the script

The secrets are fetched over the one-time token — no SSH from WHMCS and no hand-copied credentials are involved.