Can we deploy content directly to publish in aem cloud?

[Mario248]

We have a package that contains AEM pages and DAM files, around 800MB in size. In AEM prem, as a best practice, we usually log in separately to both author and publish instances to deploy the AEM packages. This approach allows us to uninstall the package from either instance in case of any issues. However, in AEM Cloud, this doesn't seem feasible because we can't directly log into the publish instance due to the auto-scaling nature of the cloud pods.

The only available option appears to be installing the package on the author instance and then replicating it to the publish instance. However this approach doesn't allow us to uninstall content from the publish instance if there's a need to revert changes. Is there any alternative option available to handle this scenario effectively?

[daniel-strmecki]

Hi @Mario248,

in AEMaaCS I would not recommend creating content in lower-level environments and then pushing it to Production. A better strategy is to setup content directly in Production Author. Now obviosuly content should not go live before its properly tested on publish. You can achieve this on Production by:

• Not setting up the domain until the content is properly tested
• Set up basic auth for the site until the content is properly tested

Then you can use Content Backflow in Cloud Manager (see Content Sets and Copy Content Activity options) to move production content to lower-level environments for testing purposes.

Hope this helps,

Daniel

[Jörg_Hoh · Accepted solution]

Why do you deploy 800 megabytes of pages and assets to your (PROD) author and publish instances? On which environment do you create the content of this package? And what was the role of the PROD authoring instance in your setup? Did you use it to create and maintain PROD content?

In AEM it was alway the evangelized way to create the content in PROD author and then activate it. Activating content in large packages was a vehicle for workflows. The focus was always, that you can create, change and manage at a page/asset level, and that you should not rely on an one-or-nothing approach (which I read from your description). 

[kautuk_sahni]

@Mario248 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!