any way to create usable URL for cloud AEM author instances, instead of https://author-p29345-f121051.adobeaemcloud.com/ etc.

[TB3dock]

We have 7 AEM cloud envs, e.g. 

dev = https://author-p29234-f121051.adobeaemcloud.com/

uat = https://author-p23425-e098098.adobeaemcloud.com/

prod = https://author-p29345-f121058.adobeaemcloud.com/ 

etc.

The problem is, it's impossible to remember these, or know which env you are on.

You might think you are on dev, create or delete some content, then realise its uat, screwing up the testing.

Is there any way to create a nice name/url?  

Neither DNS CNAMES nor Aliases work.

[Asutosh_Jena_ · Accepted solution]

Hi @TB3dock 

No there is no way we can update these URLs.

But you can think of using "AEM Environment Indicator" from ACS Commons with which you can define a color code for each of the environment and using that you can identify which environment it is.

https://adobe-consulting-services.github.io/acs-aem-commons/features/environment-indicator/index.htm...

Thanks!

[TB3dock]

Hi, thanks for that. Unfortunately, this article only applies to on prem AEM. Cloud AEM does not allow editing or viewing of the OSGI properties. We can do it through code, but for that we need to know the name of the osgi configuration file. Any ideas what this might be?

[Asutosh_Jena_]

Hi @TB3dock 

Yes AACS does not allow us to view the OSGi Property but you can try this on your local AACS instance first to see what configuration it is.

Here is the configuration:

com.adobe.acs.commons.wcm.impl.AemEnvironmentIndicatorFilter.xml

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
    jcr:primaryType="sling:OsgiConfig"
    browser-title-prefix="Author"
    css-color="#FF7F50"
    inner-html="Author"/>

You can create similar one for AACS as well. 

[TB3dock]

Awesome thanks! How could I try it on my local env? I can view or edit existing osgi configs here: http://localhost:4502/system/console/configMgrn but there is no option to create a newone (that I can find). Also, I dont belive the local env has any kind of usable identifier, e.g. its not dev, stage or prod.  I am guessing I can only test this on envs with those 3 designations.

[Asutosh_Jena_]

@TB3dock You can start your local AEM instance with "dev" run mode, by adding the below property in sling.properties file which is located under <AEM installation directory>/crx-quickstart/conf.

sling.run.modes=dev, author

You can create the OSGi configuration as I mentioned above and test it on local.

Inner HTML will add a text showing as "author" along with the color.

[Asutosh_Jena_]

Hi @TB3dock 

I have configured my local AEM as Cloud Service instance to run with "dev" run mode and added the OSGi configuration in code to identify the dev instance with green color code.

Just ensure you have ACS Commons https://adobe-consulting-services.github.io/acs-aem-commons/ installed on your instance.

Thanks!

[TB3dock]

Whats AACS?

[Asutosh_Jena_]

@TB3dock It's AEM as Cloud Service.

[TB3dock]

what does inner-html do?

[Asutosh_Jena_]

It will add a Text as "Author" along with color on your browser to identify it's Author.

Let's say you want to keep green color for development environment, then you might get confused with author and publish. So you can use green with "author" as the inner-html for author instance and green with "publish" as the inner-html for publish instance.

[TB3dock]

We tried this. it only works for dev. for stage and prod, it also shows dev.  This appears to be a limitation of the cloud AEM.  It works for non cloud only.

[Bimmi_Soi]

Hi @TB3dock ,

There is no way we can change the urls, but Adobe is working on this.

Custom Author environments' domains - Adobe Experience League Community - 413262

As suggested by @Asutosh_Jena_, you can use "AEM Environment Indicator" .

Hope this helps!!
Thanks