How to move assets from dev to production in AEMaaCS | Community
Skip to main content
Mario248
Mario248
Level 7
November 10, 2022
Solved

How to move assets from dev to production in AEMaaCS

  • November 10, 2022
  • 2 replies
  • 1245 views

In AEMaaCS, I would like to move 10GB of assets from development to production. Can I move 10GB assets from the dev cloud to the production cloud using the package manager? I would appreciate it if you could suggest an alternative method.

 

Do we need any CSE help to deploy the package in AEMaaCS as we do on AMS?

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 krati_garg

Hi @knan 

There are two ways:
1. Move it by Package Manager. Ideally, the size of Package depends upon the Network Bandwidth. Have seen customers building Content Package as high as 1GB. There is no official limit to the size of your package. 10GB Content can easily be broken into multiple packages and uploaded to higher environments.

2. If the migration is from AMS to AEMaaCS, you might have already leveraged on CTT to get Content from AMS to AEMaaCS Dev. If the content is almost same, then consider using CTT to get the Content on Production from AMS, and then identify the delta Content on Dev Environment, and take the Package Manager approach for Delta Content on Dev

Please note that the Content Tool which is to be released by Adobe in near future is supposed to sync Content from Prod to Non Prod i.e Backward flow and not the Upward flow

2 replies

K
Community Advisor
KNanCommunity Advisor
Community Advisor
November 10, 2022

Hi

Please refer this ,

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/migrating-assets-from-one-cloud-instance-to-other/m-p/556016

 

Thanks

    krati_garg
    Adobe Employee
    krati_gargAdobe EmployeeAccepted solution
    Adobe Employee
    November 10, 2022

    Hi @knan 

    There are two ways:
    1. Move it by Package Manager. Ideally, the size of Package depends upon the Network Bandwidth. Have seen customers building Content Package as high as 1GB. There is no official limit to the size of your package. 10GB Content can easily be broken into multiple packages and uploaded to higher environments.

    2. If the migration is from AMS to AEMaaCS, you might have already leveraged on CTT to get Content from AMS to AEMaaCS Dev. If the content is almost same, then consider using CTT to get the Content on Production from AMS, and then identify the delta Content on Dev Environment, and take the Package Manager approach for Delta Content on Dev

    Please note that the Content Tool which is to be released by Adobe in near future is supposed to sync Content from Prod to Non Prod i.e Backward flow and not the Upward flow

      Terms & ConditionsAccessibility statement

      Loading footer...