How to configure mixed content sources (Google Drive + AEM) in fstab.yaml?

[yjwu321]

Hi everyone,

I am working on an Edge Delivery Services project and trying to implement a hybrid content source setup.

My Goal: I want to serve the site root (/) from a Google Drive folder, while serving a specific sub-path (/eds) from AEM Author (Universal Editor).

Current Configuration:

fstab.yaml:

I defined two mountpoints like this

mountpoints:
  # Root served from Google Drive
  /: https://drive.google.com/drive/folders/MY_GDRIVE_FOLDER_ID
  
  # /eds sub-path served from AEM
  /eds:
    url: "https://author-pXXXX.adobeaemcloud.com/bin/franklin.delivery/my-org/my-repo/main"
    type: "markup"
    suffix: ".html"

paths.json:

I attempted to map the AEM content path to the /eds/ prefix

{
  "mappings": [
    "/content/my-site/:/eds/"
  ]
}

The Issue: It seems that only the root mountpoint works. When I try to access pages under /eds/, they do not resolve to the AEM content correctly.

Question: Is it supported to have multiple mountpoints mixing Google Drive and AEM in a single fstab.yaml? If so, did I miss any configuration steps (e.g. in paths.json)? Or is this a known limitation where a project is restricted to a single content source?

Any advice would be appreciated. Thanks!

[VishalKa5 · Accepted solution]

Hi @yjwu321 ,

Why your setup does not work

• fstab.yaml does not support hybrid content sourcing

• Only one mountpoint can act as the site root

• The first mountpoint (/) defines the entire content source

• Sub-path mountpoints (like /eds) do not override the primary source

• paths.json:

  • Only maps content paths > URLs

  • Does not switch content sources

  • Cannot redirect part of the site to AEM

So even though your configuration looks valid syntactically, EDS will never route /eds to AEM when / is already mapped to Google Drive.

Important clarification

fstab.yaml is for choosing where content comes from, not for combining sources.
paths.json is for URL rewrites, not for content resolution.

---

What is supported instead (recommended options)

Option 1: Use AEM as the single source

• Use AEM Author + Universal Editor for / and /eds

• Recommended if you need structured or authored content

Option 2: Separate sites (recommended for hybrid needs)

• Site A (Google Drive content)
  example.com/

• Site B (AEM content)
  eds.example.com/ or /eds via reverse proxy

Option 3: Proxy AEM content into the site

• Fetch AEM-rendered content via:

  • Edge functions

  • Static fetch + embed

• Treated as external content, not first-class EDS content

Thanks

[yjwu321]

Got it. Thanks a lot!