Adobe Experience Cloud
AEM Cloud Manager variables can change without a deployment trail
Build a change record for AEM Cloud Manager environment variables that alter production behavior.
November 9, 2026
A deployment can be unchanged while an AEM application starts behaving differently. Adobe documents that Cloud Manager environment variables can be updated without a code deployment and take effect immediately. A community feature request asks for actor, timestamp and revision history for those changes, because the current configuration alone does not explain a past incident.
Make configuration part of change control
Inventory variables by program, environment, service scope and owner. For each proposed production change, record the ticket, approver, old non-secret state, intended new state, application behavior expected and rollback decision. For secrets, record a version identifier or rotation event; do not copy secret values into the ticket. Time-stamp the action in UTC and keep the operator or service-account identity.
Adobe's OSGi configuration guidance explicitly says customers should govern and integrate values that live outside Git into their deployment process. That gives the team a concrete control to implement today even if the requested Cloud Manager audit feature is not available.
Investigate an unexplained change
Compare current variable names and scopes with the last approved snapshot. Correlate that difference with application logs, Cloud Manager activity and the exact time users first saw the symptom. A poll can reveal a difference but may miss intermediate changes and cannot prove who acted. Where the UI, API or CLI is used, route all three through the same approval and recording process.
Do not confuse a missing deployment with evidence that no configuration changed. Rehearse a rollback for the specific service and verify the restored behavior.
Adovo’s view
Configuration is code in its effect, even when it sits outside the repository. Give every variable a named owner and every production change a trace. The quickest incident response begins with knowing what changed.
