ECE and ECH: added relation between secure settings and user settings

[eedugon]

Closes https://github.com/elastic/docs-projects/issues/466

I've added an improvement in ECE docs, explaining the relation between the secure settings and standard user settings (when a feature requires both types of settings, secure settings need to be configured first to avoid cluster restarting issues (bootloops) ).

Let me know your thoughs, @shainaraskas .

I've added cross comments in:

• ECE user settings page (important banner because secure settings should be updated first)
• ECH user settings page (important banner for the same reason)
• Secure settings page (not marked as important).

On top of that I've changed the headings of all examples, as H2 was showing the titles too big.

[shainaraskas]

eck is safe from auto restarts?

[eedugon]

On eck you can change both at the same time, which should be considered kind of obvious IMO (no need to mention it). The problen with ECE and ECH is that the settings are configured in completely different places, so it’s technically impossible to configure a certain feature in a single step if it requires secure + normal settings Edu González de la Herrán Senior Technical Writer @ Elastic *Please note: Emails may be stored and shared to provide a better customer experience. To learn more about how we use your information, please review Elastic’s **Privacy Statement. * <https://www.elastic.co/legal/privacy-statement> El El jue, 17 abr 2025 a las 18:05, shainaraskas ***@***.***> escribió:

…

***@***.**** approved this pull request. eck is safe from auto restarts? ------------------------------ In deploy-manage/deploy/cloud-enterprise/edit-stack-settings-elasticsearch.md <#1190 (comment)> : > -::::{note} -ECE blocks the configuration of certain settings that could break your cluster if misconfigured, including some zen discovery and security settings. For a list of settings that are generally safe in cloud environments, refer to the [{{es}} configuration reference](elasticsearch://reference/elasticsearch/configuration-reference/index.md). -:::: +:::{important} +If a feature requires both standard `elasticsearch.yml` settings and [secure settings](/deploy-manage/security/secure-settings.md), configure the secure settings first. Updating standard user settings can trigger a cluster rolling restart, and if the required secure settings are not yet in place, the nodes may fail to start. In contrast, adding secure settings does not trigger a restart. ⬇️ Suggested change -If a feature requires both standard `elasticsearch.yml` settings and [secure settings](/deploy-manage/security/secure-settings.md), configure the secure settings first. Updating standard user settings can trigger a cluster rolling restart, and if the required secure settings are not yet in place, the nodes may fail to start. In contrast, adding secure settings does not trigger a restart. +If a feature requires both standard `elasticsearch.yml` settings and [secure settings](/deploy-manage/security/secure-settings.md), configure the secure settings first. Updating standard user settings can trigger a cluster rolling restart, and if the required secure settings are not yet in place, the nodes might fail to start. Adding secure settings does not trigger a restart. ------------------------------ In deploy-manage/deploy/cloud-enterprise/edit-stack-settings-elasticsearch.md <#1190 (comment)> : > +## Examples + +### Enable email notifications [ece_enable_email_notifications_from_gmail] I suggest you put this back together because it's just one example — Reply to this email directly, view it on GitHub <#1190 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGBFXJI53CJUUQ2KFIMHRM32Z7GOJAVCNFSM6AAAAAB3KSNXIWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDONZWGI3TENBXHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>