Custom cloud config in aemaacs | Community
Skip to main content
C
cmanoha1
New Participant
November 23, 2022
Solved

Custom cloud config in aemaacs

  • November 23, 2022
  • 2 replies
  • 1249 views

We're migrating to aemaacs from AEM 6.5. We have a custom cloud configuration in place for datalayer. We followed this guide - https://experienceleague.adobe.com/docs/experience-manager-64/developing/extending-aem/extending-cloud-services/extending-cloud-config-custom-cloud.html?lang=en in initial setup. 
Is there any such guide for aemaacs? We're not able to get the existing config work for cloud publisher. While running repoinit script to set ACL for anonymous user we're facing PathNotFoundException for /etc/cloudservices/*.

Any help appreciated.
Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by aanchal-sikka

hello @cmanoha1 

 

repo-init scripts execute at the time of deployment on AEM Images. Thus, they are capable of setting permissions on both mutable and immutable paths.

 

The repo-init can set ACL only if a node already exists. Thus, if we receive PathNotFoundException, it means that /etc/cloudservices/* isn't available when repo-init is executing, during deployment

 

To resolve the same, create these paths with proper primaryType via repo-init. This would assure that the path is available, while setting ACLs. Example:

 

 

{
    "scripts": [
          "create path /etc/cloudservices(sling:Folder)\n\n",
          "create path /etc/cloudservices/aemdatalayer(cq:Page)\n create path  /etc/cloudservices/aemdatalayer/jcr:content(cq:PageContent)\n\n",
          "set ACL on /etc/cloudservices/aemdatalayer\n\tallow jcr:read for \"anonymous\"" ] }

 

2 replies

aanchal-sikka
aanchal-sikkaAccepted solution
New Participant
September 5, 2023

hello @cmanoha1 

 

repo-init scripts execute at the time of deployment on AEM Images. Thus, they are capable of setting permissions on both mutable and immutable paths.

 

The repo-init can set ACL only if a node already exists. Thus, if we receive PathNotFoundException, it means that /etc/cloudservices/* isn't available when repo-init is executing, during deployment

 

To resolve the same, create these paths with proper primaryType via repo-init. This would assure that the path is available, while setting ACLs. Example:

 

 

{
    "scripts": [
          "create path /etc/cloudservices(sling:Folder)\n\n",
          "create path /etc/cloudservices/aemdatalayer(cq:Page)\n create path  /etc/cloudservices/aemdatalayer/jcr:content(cq:PageContent)\n\n",
          "set ACL on /etc/cloudservices/aemdatalayer\n\tallow jcr:read for \"anonymous\"" ] }

 

Aanchal Sikka
    SantoshSai
    SantoshSai
    New Participant
    November 23, 2022

    Hi @cmanoha1 ,

    Can you just pass script from init if possible?

    Regards,

    Santosh

    Santosh Sai
      C
      cmanoha1Author
      New Participant
      November 23, 2022
      {
    "scripts": [
        "set ACL on /etc/cloudservices/aemdatalayer\n\tallow jcr:read for \"anonymous\""
    ]
}

      This is under config.publish by name org.apache.sling.jcr.repoinit.RepositoryInitializer~<project-name>.cfg.json

        SantoshSai
        SantoshSai
        New Participant
        November 23, 2022

        @cmanoha1 - 

        The problem would be because the repo init statements mention mutable content in the documentation[0].

        /apps and /libs are immutable at runtime and ACLs are stored under the respective nodes that need the permission in AEM. 

        [0]: https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/developing/basics/mutable-immutable.html?lang=en

         

        Santosh Sai
          Terms & ConditionsAccessibility statement

          Loading footer...