/etc Sling mapping deployment to AEMaaCS

[zeiss_hs]

Hi,

As the separation of pipeline is available for AEMaaCS to deploy dispatcher configuration, we're having scenarios where we need to make frequent changes to sling mapping and dispatcher config. So, deploying dispatcher config is quick instead of running full deployment. 

Is there any quick way to deploy sling mapping configs as well quickly without initiating the full project pipeline?

Also, just to reconfirm, even in cloud, the sling mapping path remain same i.e. /etc/ and has no restructure for it, right?

Best regards,
Himanshu Singhal 

[Jineet_Vora · Accepted solution]

@zeiss_hs - There are multiple ways to enable redirects for content at AEM, Dispatcher and CDN level. Due to the nature of AEMaaCS, immutable nodes like /etc cannot be modified without a deployment pipeline. Also, /etc/map/http is an old way to define redirects.

There are 3 ways to define a redirect in AEMaaCS:

1. CDN level

2. Dispatcher level (mod_rewrite module)

3. Page level using page properties (Authors can define redirect path and type (301/302) at page level)

4. Redirect manager (ACS Commons)

More details can be found here: https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/administration/url-redir...

Hope this helps!
Jineet