How to resize a customer's bucket quota

A customer asks for more (or less) storage. Here's where to change the quota, how it applies, and how it interacts with WHMCS billing.

Last updated 20 days ago

How to resize a customer's bucket quota

When you'd do this

A customer requests an upgrade ("I'm running out of room"), a downgrade, or you want to manually grant headroom while a billing change goes through. ImpulseMinio supports both per-service quota overrides and plan changes — they behave differently, and which one you want depends on whether billing should change too.

Two paths, two behaviours

Path | Use when | Billing effect

Adjust quota on the service directlyOne-off override, support gesture, temporary headroomNone — billing stays on the customer's current plan
Change the WHMCS product to a different planThe customer is permanently moving up or down a tierWHMCS prorates and bills the difference per its standard upgrade flow

Path A — adjust the service quota directly

  1. Open the customer's service in WHMCS. Go to the Module tab. ImpulseMinio renders an admin panel with the current storage, bandwidth, bucket count, and access-key count.
  2. Edit the Storage MB field (and Bandwidth GB if relevant) to the new value. Save.
  3. The new quota applies on the next quota-sync cron tick (typically within minutes). The addon calls the MinIO admin API to update the bucket's setBucketQuota value. The customer's uploads against the bucket are immediately capped at the new value once the call lands.
  4. An audit-log entry is written to mod_impulsecore_audit_log with the old value, new value, and your admin user. Use this for support history and billing disputes.

A quota override on the service persists across plan changes — if you grant a customer +50 GB headroom and they later upgrade plans, that override stays in place unless you reset it. There's typically a Reset to Plan Default button on the Module tab.

Path B — change the plan in WHMCS

  1. Open the customer's service. In the Product/Service block, click Upgrade/Downgrade.
  2. Pick the new product / configurable option. WHMCS calculates proration and shows the credit/charge.
  3. Apply. WHMCS raises the invoice, processes payment per its configured workflow, and fires the upgrade hook ImpulseMinio listens for. The addon then updates the quota to the new plan's value on the next provisioning cron tick.
  4. The customer gets a WHMCS notification through whichever email templates you have configured. ImpulseMinio doesn't send a separate notification by default.

Things to know

  • Downgrading below current usage: the addon will not silently delete objects. If the new quota is below current usage, the bucket is marked over-quota — uploads return HTTP 403 until the customer deletes objects or you raise the quota again. The MinIO admin behaviour around setBucketQuota with a value below current usage is preserved.
  • Replication / migration plans (Licensed tier): changing replication caps typically takes effect immediately on new replication job creation, but existing replication jobs in flight aren't reconfigured retroactively in most installs. Check the audit log after the quota change to confirm the expected behaviour for your install.
  • Application is asynchronous. Both paths depend on the next Core cron tick to push the change to MinIO. If you need it immediate, you can run Core's cron.php manually after saving — see How to monitor storage usage for the command.

Related