Configuration Editor (Administrators)

The Configuration Editor is an administrator page in the web interface that lets you review and change your cluster's configuration settings without leaving the browser. It is an alternative to editing settings directly in the AWS console.

Administrators only

The Configuration Editor is available to cluster administrators. It uses the same access controls as the rest of the admin area.

Prefer the web interface over the console

Editing settings here keeps a record of every change (who changed what, and when) and warns you when a change needs a service restart. Editing the same settings directly in the AWS console does not give you those safeguards.

Find a setting

The editor presents every configuration setting in two ways:

• Browse. A tree on the left groups settings by area (for example, web interface, scheduler, virtual desktops). Expand a group to see the settings inside it.
• Search. Use the search bar to jump straight to a setting by name, or to find settings whose value contains a term.

Each setting shows its current value, its type (for example on/off, number, or text), and a short description of what it controls.

Some settings are hidden or read-only

A few sensitive settings (such as internal secrets) are never shown, and some settings are shown for reference but cannot be edited. This is by design and protects your cluster.

Edit and apply changes

Changes are staged first, so you can review everything before it takes effect:

1. Open a setting and change its value. The editor picks the right control for the setting's type (a toggle, a number field, or a text or structured editor).
2. Edited settings are marked so you can see exactly what you have changed.
3. Review your pending changes, then click Apply to save them.

Changes are validated before they are saved. If a value is not allowed (for example, a number outside the permitted range), that change is rejected and the editor tells you why. When you apply several changes at once, each one succeeds or fails on its own, and the editor shows the result for each.

When a change needs a restart

Most settings take effect within a few seconds of being applied. Some settings only take effect after the affected service is restarted.

When your pending changes include one of these, the editor shows a warning that names the service involved and tells you how to restart it.

The editor never restarts services for you

Applying a change always saves the new value immediately, but for settings that require a restart, the new value only takes effect once you restart the named service yourself from the controller. The Configuration Editor never restarts a service on its own. Never restart the web interface from within the web interface.

Review history and who changed what

Every change is recorded. For any setting you can:

• See its history of previous values.
• See who last edited it and when.
• Revert to an earlier value. Reverting saves the older value as a new change (the history is never rewritten), so the full record is preserved.

A cluster-wide activity view shows recent changes across all settings, so you can see at a glance what has changed and by whom.

Apply risky changes with an automatic rollback

For changes that could affect your own access to the cluster (for example, settings that require a restart), you can choose to apply them with an automatic rollback timer. If you do not confirm that everything still works within the time window, the change is rolled back to its previous value automatically. This option appears when it applies to your pending changes.