Skip to main content
Level 2
Nov 4, 2025 5:54 PM UTC
Solved

Does anyone have an idea on how to create a custom domain for AEMaaCS authoring environment?

I realize from https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/custom-domain-names/introduction that creating a custom domain in Cloud Manager is not possible for the authoring environment.

Does anyone have a suggestion on an alternate option if we preferred to have a 'Vanity URL' for access to our authoring environment?
(ie: author.company.com vs author-p000000-e0000000.adobeaemcloud.com)

I have tried DNS CNAME records to point to author-p000000-e0000000.adobeaemcloud.com, but that of course does not work...
My only other thought was to have the CNAME record point to a local web instance, and create an http redirect from there, but I'm trying to avoid the multiple hoops.

Any other ideas appreciated.
Thank you.

muskaanchandwani
muskaanchandwaniAccepted solution
Adobe Employee
Nov 4, 2025 6:06 PM UTC

Hello @jasontr7 

Yes, custom Domain is not supported for AEMaaCS Author and there is no official Workaround for it.

However, one user has implemented the following workaround approach to simulate a Custom Domain configuration :

>> Since you can't set up an author domain, the trick is to set up a redirect from a custom domain to the AEMaaCS author domain.

Let's assume the following:
• Custom "author" domain is author.mysite.com
• AEMaaCS author domain is author-p12345-e123456.adobeaemcloud.com

Since we cannot configure a redirect / rewrite / apache rule on the author, the redirect must be implemented on publish.

• Register author.mysite.com as an additional domain for the publish environment.
• Set up an additional vhost config for author.mysite.com
• Configure nothing but a 301 redirect to author-p12345-e123456.adobeaemcloud.com

The editor's http request is then sent once to Apache publish. Apache redirects the editor to the AEMaaCS author domain.
As a result, the URL in the browser will change from https://author.mysite.com to https://author-p12345-e123456.adobeaemcloud.com.

The author can use his existing bookmarks / an easy to remember URL for the (initial) request.

3 replies

muskaanchandwani
Adobe Employee
muskaanchandwaniAdobe EmployeeAccepted solution
Adobe Employee
Nov 4, 2025 6:06 PM UTC

Hello @jasontr7 

Yes, custom Domain is not supported for AEMaaCS Author and there is no official Workaround for it.

However, one user has implemented the following workaround approach to simulate a Custom Domain configuration :

>> Since you can't set up an author domain, the trick is to set up a redirect from a custom domain to the AEMaaCS author domain.

Let's assume the following:
• Custom "author" domain is author.mysite.com
• AEMaaCS author domain is author-p12345-e123456.adobeaemcloud.com

Since we cannot configure a redirect / rewrite / apache rule on the author, the redirect must be implemented on publish.

• Register author.mysite.com as an additional domain for the publish environment.
• Set up an additional vhost config for author.mysite.com
• Configure nothing but a 301 redirect to author-p12345-e123456.adobeaemcloud.com

The editor's http request is then sent once to Apache publish. Apache redirects the editor to the AEMaaCS author domain.
As a result, the URL in the browser will change from https://author.mysite.com to https://author-p12345-e123456.adobeaemcloud.com.

The author can use his existing bookmarks / an easy to remember URL for the (initial) request.

Translate
ManviSharma
Adobe Employee
Adobe Employee
Nov 4, 2025 6:43 PM UTC

Hello @jasontr7 ,

 

You're correct , AEM as a Cloud Service does not support custom domains (vanity URLs) for the authoring environment. The author tier runs within Adobe’s managed infrastructure, and SSL certificates are only issued for *.adobeaemcloud.com domains.

As a result, configuring a DNS CNAME to point to the author URL will not work due to SSL and host header restrictions.

Recommended approach:
Create an internal redirect (e.g., via Nginx/Apache or corporate proxy) where author.company.com issues an HTTP 301 redirect to the official Adobe author URL (author-p000000-e0000000.adobeaemcloud.com).

This provides a clean vanity entry point while remaining compliant with Adobe’s supported configuration.

Translate
JasonTr7Author
Level 2
Nov 4, 2025 8:13 PM UTC

Thank you both.  I believe both of these options will work.
I'm going to discuss internally on which direction we will proceed.

Again, appreciate the input! 

Translate