Hi, The content flows from author to publisher and you can manage your custom workflows only on author and push the content to publisher hosted anywhere. I am not sure if AMS can allow this but in general, you should be able to push the content from author server (on-prem) to any AEM publisher serve...

Hi,

Here are some good articles which talks about self hosting vs AMS:http://www.jetteroheller.com/adobe-managed-services-vs-self-hosting-aem-pros-cons/ https://www.albinsblog.com/2018/09/adobe-experience-manageraemon-premises-to-AMS-cloud.html#.X0vThWdKhTY 

If you're referring this on publisher then, you should disable all Link Checker service configs. On author, try modifying the Day CQ Link Checker Transformer: remove a:href from the Rewrite Elements config.

It depends on your customization (Static/Editable templates). If you're not customizing anything then it would store here:/content/yourpagepath/jcr:content/image. If you look at the property of fileReference then you'll the image ref path. You'll have to use Server Side script (JavaScript API) or us...

One single AEM instance to host both application would be recommended for easy maintenance and cost-effective. You can restrict the gated content to your organization and allow the other content to be public. Going to the cloud/AMS vs hosting on-prem (or on your cloud infrastructure) have its pros/c...

We're facing the similar issue with Brand Portal integration. The client secret keeps on dropping and we noticed that the older bundles installed are the culprit. If you have done in-place upgrade from older versions then their might be unwanted SP/CFP bundles. You can safely uninstall those bundles...

I don't think the CM supports the profiles. You can create a two different release branches for each site and checkin the changes to those respective branches individually. You can use the release branch to deploy them to AMS servers using CM. After deployment, merge those release branches back to m...

 First of all, the above snippet is used to append the /content/myproject/* path to your incoming shortened urls. Ex: www.example.com/mypage.html would resolve to: server:port/content/myproject/en/mypage.html. The highlighted part would vary based on project implementation. All other urls would go p...

Have a different URI and handle them at Apache/Dispatcher to PT (to maintain the same URL) or redirect to /api/*. This would be the easy one for maintenance. To use PT and retain the original URI/URL:RewriteRule ^your/custom/uri/$ /api/your/path.json [PT] The above would internally redirect the requ...