Guidance on EDS site creation using adobe repo | Community
Skip to main content
V
VishnuRa5
Level 2
March 26, 2026
Question

Guidance on EDS site creation using adobe repo

  • March 26, 2026
  • 1 reply
  • 12 views

Hi everyone,

I’m currently working on setting up an Edge Delivery Services (EDS) site using an Adobe repository and would appreciate some guidance.

My goal is to:

  • Set up a new EDS project using the official Adobe repository

  • Configure the required integrations to create and load the website using AEM Sites authoring

  • Create pipelines, deploy the site, and preview content

I’ve gone through the documentation, but most of the references are based on using a public GitHub repository. In my case, I’m working with a private repository (Adobe repo).

At the moment, I’m facing an issue with site ownership verification. Even after adding the required verification file, the verification is not successful. Currently, my repository only contains this verification file and does not yet include files like fstab.yaml or other standard EDS configuration files.

It would be really helpful to understand the correct approach for private repository setups, EDS site creation, especially around ownership verification and when to introduce standard configuration files like fstab.yaml.

Any guidance, suggestions, or relevant resources would be greatly appreciated.

Thanks in advance!

 

1 reply

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity Advisor
Community Advisor
March 26, 2026

Hi ​@VishnuRa5 

1. Make sure the EDS site actually exists and is live

Before Cloud Manager can verify the repo, the Edge Delivery site must resolve:

  • Create the site either:
    • via Cloud Manager > Edge Delivery > Create site now, or
    • from the boilerplate (adobe/aem-boilerplate) + BYO Git onboarding.
  • Confirm you can open: 
    https://main--<site>--<org>.aem.live/ (any 200 page is fine)

    Cloud Manager's validator calls the EDS origin; an empty/non-onboarded repo (only the challenge file, no site) usually gives 404 and verification fails.

2. Create the correct challenge file for EDS

In the main branch of the Edge Delivery repo for that site:

3. Temporarily disable site authentication (if used)

If your EDS site uses Helix/EDS auth ("protected site"), .page often returns 401, which breaks verification:

4. When to add fstab.yaml / config files?

For Helix 5 / modern EDS, fstab.yaml is no longer required; content sources are configured via admin / site config

You can add fstab.yaml, paths.yaml, blocks, etc. after:

  • The site is live on main--<site>--<org>.aem.live.
  • Repo ownership is verified in Cloud Manager.

These files do not affect the repo-ownership check; only the challenge file and its HTTP 200 response matter.

5. If you are using a private external repo (BYO Git)

If the "private Adobe repo" is an external Git (GitHub Enterprise / GitLab / Bitbucket) onboarded via Repositories > Add external repository:

Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
Terms & ConditionsAccessibility statement

Loading footer...