Hi @YAMINIK1
In AEM Edge Delivery Services (EDS), content can appear in Preview or Live environments even if you don’t see a YAML configuration in the repo because not all EDS setups require a YAML file for mountpoints or content sources. Here’s why:
Content Source in EDS
- Edge Delivery Services can fetch content from multiple sources:
- AEM Author/Publish instance (via the AEM GraphQL or REST API)
- Connected cloud storage (Google Drive, S3, etc.)
- The connection details (mountpoints, credentials, paths) can be configured:
- Directly in the environment settings (via AEM Cloud UI or Edge configuration console)
- Via the AEM Cloud Manager / service account
This means the YAML file in the repo is optional; it’s mainly used when you want a declarative, version-controlled configuration for mountpoints. If the mountpoint is already configured in Cloud Manager or EDS console, the content flows automatically.
How Content Appears Without YAML
EDS reads the configuration from the cloud environment rather than the repo.
The environments you mentioned:
These URLs are already mapped to the content repository or mounted storage in the cloud setup. That’s why content is visible even without a YAML file in your Git repo.
Hope this helpful 🙂
Regards,
Karishma.
