Using Context aware configurations in EDS using Universal Editor

Hi @seshasai 

As of now (AEM 6.5 and AEM as a Cloud Service), Context-Aware Configuration (CAC) is not directly supported or exposed within EDS (Edge Delivery Services) or Universal Editor in the same way it's used in traditional AEM Sites implementations.

Use AEM GraphQL APIs with Conditional Logic

If you're building a front-end on EDS:

• Use GraphQL APIs to retrieve Content Fragments with metadata
• Implement context logic in your front-end (e.g., different rendering based on locale or brand)

As AEM have certain limitations like

• Context-Aware Configurations (CAC) are part of the WCM Core Configuration API.
• EDS does not yet expose CAC support like com.adobe.cq.dam.cfm.ContentFragmentCoreComponentsConfiguration.
• Universal Editor (UE) does not currently bind to AEM CAC either.
• EDS relies on Content Fragment Models, JSON APIs, and metadata to power editing experiences—not on CAC stored under /conf.

Use Custom Metadata on Content Fragments

Instead of CAC, you can store context-like configurations using metadata fields in:

• Content Fragment Models

• Content Fragments themselves

• Folder-level metadata.

Please go through Context-Aware configuration in AEM - Adobe Experience League Community - 620639.

Hope this helpful.:)

Regards,

Karishma.