Skip to main content
aanchal-sikka
Community Advisor
aanchal-sikkaCommunity Advisor
Community Advisor
Oct 13, 2025 2:34 AM UTC

Migration to AEM Cloud: AMS, Asset Share Commons, Content Hub & China Access

We are currently evaluating migrating our AEM 6.5 implementation to the Cloud Service. However, we’ve encountered a few issues and would appreciate input from organizations that have gone through similar transitions:

1. AMS and Cloud Service - Tech Parity

Adobe is recommending AMS, but it means additional operational and development costs.  AMS has not received new features at the same pace as AEM Cloud. If our organization wants to adopt new features, especially at a global scale, AMS would not have tech parity. So, features may not be available for China.

  • Has anyone faced this situation? How did your organization overcome these limitations?

2. Asset Share Commons and Content Hub User Limits

Currently, we use Asset Share Commons (ASC) with no user limits. Migrating to Content Hub imposes a 250-user limit, which seems highly restrictive.

  • For those who migrated from ASC to Content Hub, what other challenges did you face besides the user limit?

  • Any advice on scaling Content Hub for larger user bases? Are there alternatives that avoid this restriction?

3. China Access: Asset Share Commons, Content Hub, Authoring

Internet sources suggest setting up “Static Site + CDN” or “Varnish Cache in AWS” for China content delivery, to counter the latency of sites hosted outside China.

  • Have you tested Asset Share Commons performance in China? Was search functionality affected?

  • Do teams in China have access to AEM Cloud Author? If so, what challenges have you encountered (connectivity, features, compliance)?

Would appreciate feedback, advice, or sharing of experiences. Thank you!

    2 replies

    treborrenmus
    Nov 19, 2025 2:43 PM UTC

    @aanchal-sikka - We can help with China latency problem. We have solved this riddle and helped companies reduce infrastructure overhead related to the more common solutions we see. #streamx #perficient. 

    Translate
    Joyful_videographer5ad5
    Joyful_videographer5ad5
    Nov 5, 2026 9:39 PM UTC

    On the China access part of your question, from working with a few AEM customers on both Cloud Service and 6.5, with Adobe’s own docs as the reference:

    Cloud Service has no mainland China region (https://developer.adobe.com/experience-cloud/cloud-manager/guides/api-usage/creating-programs-and-environments) and the AEM-managed CDN has no mainland points of presence. Adobe’s documented path is a customer-managed CDN on the publish tier, approved case by case, with an on-call CDN team and a load test (https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn). That CDN needs an ICP, and the ICP needs a China-registered entity (https://www.aem.live/docs/china).

    A China CDN behind an ICP works fine for mostly static pages. What still crosses the border no matter where the HTML is served from, including AMS publishers inside China: Dynamic Media (Akamai delivery, with China listed as a restricted area and a separate China delivery path on an ICP’d .cn subdomain: https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-21940), Launch/Target/Analytics (Target has no China edge cluster; Analytics China collection is a paid add-on), Eloqua or Marketo form posts, and search. The HTML is local, the dependencies aren’t.

    On Author access from China, Adobe’s own line is “possible with limitations and not fully supported.” Most teams end up on a VPN by default; worth deciding that deliberately.

    Asset Share Commons: as far as I know its search runs on your publish tier, so it follows whatever path your HTML takes. The assets themselves are the Dynamic Media question above.

    I put the three options side by side with the Adobe source for each point, so you don’t have to chase them across Experience League and aem.live: https://www.21cloudbox.com/how-to-run-adobe-aem-in-china.html

     

    Translate
    Terms & ConditionsAccessibility statement

    Loading footer...