Not supported on Cloud Service
Converting OSGi configurations to .cfg.json for AEM Cloud Service
OSGi configuration on Cloud Service comes only from Git through the Cloud Manager pipeline, in .cfg.json format. The Web Console is not available to change values at runtime.
What to use instead
.cfg.json files in ui.config, with secrets and per-environment values supplied by Cloud Manager environment variables ($[secret:NAME] and $[env:NAME]).
How to fix it
- Convert each configuration to .cfg.json.
- Move passwords and API keys to Cloud Manager secret variables.
- Move configuration that was changed in production through the Web Console (BPA code UMI) into Git.
AEM 6.5
# com.acme.ApiClient.config
endpoint="https://api.example.com"
timeout=I"5000"Cloud Service
{
"endpoint": "$[env:ACME_API_ENDPOINT;default=https://api.example.com]",
"timeout": 5000,
"apiKey": "$[secret:ACME_API_KEY]"
}How we detect it
- Readiness scan rule
legacy-osgi-config: OSGi configs in .config, .cfg or XML node format.
Best Practices Analyzer reports it under UMI, URC.
Can agents fix it?
High.
Source: Adobe Experience League. Checked 19 October 2026.