Making sense of configuration in AEM as a Cloud Service

Adobe Experience Manager as a Cloud Service (AEMaaCS) introduced a stricter and more explicit approach to configuration management. Configuration is no longer a runtime concern but a core part of application architecture, deployment, and governance.

This overview summarizes the primary configuration models available in AEMaaCS and their intended use cases. For a deeper explanation, architectural guidance, and practical examples, see:
https://medium.com/@konstantyn.diachenko/making-sense-of-configuration-in-aem-as-a-cloud-service-7f2fc567e58d

OSGi Configuration

OSGi configurations define technical and behavioral aspects of code execution, such as:

• Service wiring

• Feature flags

• External integrations

• System thresholds and limits

In AEMaaCS, OSGi configurations are:

• Immutable at runtime

• Deployed through CI/CD

• Parameterized using environment variables where needed

Use OSGi configuration when values are developer-owned and affect application behavior.

Context-aware configuration

Context-Aware Configurations (CA Configs) support content- and site-specific variation, including:

• Brand or site-level settings

• Language or region behavior

• Author-controlled decisions

Key characteristics:

• Stored within content hierarchy

• Inherited by structure

• Editable by authors with proper governance

Use CA Configs when configuration depends on site context rather than environment.

Cloud environment variables

Cloud environment variables are used for environment-specific and sensitive values, such as:

• Secrets and credentials

• External service endpoints

• Environment-dependent toggles

These values are managed outside of code and content and injected at runtime.

Use environment variables when values differ by environment or must remain secure.

Choosing the correct model

Selecting the correct configuration type depends on:

• Ownership (developer vs author vs platform)

• Scope (code, content, environment)

• Frequency of change

• Security requirements

Using the appropriate model improves deployment safety, clarity of ownership, and long-term maintainability.

Key takeaways

• AEMaaCS enforces clear configuration boundaries

• OSGi, Context-Aware Configs, and environment variables serve distinct purposes

• Correct model selection is essential for safe cloud deployments