How to replicate a dam asset from aem publisher to author environment in AEM as cloud

Hey ​@JavedZi , there are two architectural issues here worth flagging before going further.

Issue 1 Writing the file on Publish
Publish in AEMaaCS is stateless and runs as multiple pods. Any file written there will not persist. It may disappear on the next deployment or may not be visible across all pods. Publish is purely a content delivery layer, not a storage layer.

Issue 2 Reverse replication
Content flow in AEM is strictly Author to Publish, never the other way. Adobe deprecated reverse replication in AEMaaCS for this reason.

The right approach using Adobe I/O (App Builder)

Keep it simple:

1. On Publish, instead of writing the file, make an HTTP call to an App Builder action with the user data as the payload
2. The App Builder action generates the Excel and either stores it externally (Azure Blob, S3, SharePoint) or pushes it to Author DAM using the AEM Assets HTTP API

No file writing on Publish and no reverse replication needed. Publish stays stateless and the data is stored in the right place.

Hope this helps

Thanks

Veena

Hello ​@JavedZi No — in AEM as a Cloud Service you should not move that Excel from Publish → Author using reverse replication.
Reverse replication from Publish to Author is not supported in AEMaaCS, and Adobe's guidance is to use an external persistence store instead of relying on publish-tier writes flowing back into author. Also, the built-in publish-tier data synchronization only synchronizes user/profile data under /home across publish nodes, not back to author.

There is no supported direct Publish → Author replication path for your Excel in AEM as a Cloud Service.
Use external storage as the handoff point, and optionally pair it with Adobe I/O Events so author can process it automatically.

This is an anti-pattern in AEM as a Cloud Service (and most likely in all other versions of AEM). You usually have a couple of options:

• Store this in an external system rather than AEM (some options mentioned in other replies include App Builder Storage, AWS, Azure, etc.).
• Store it directly in Author. This has traditionally been the most common approach when you don’t have an external solution—you write in Author (via a service that you expose and your application from publisher can hit) and then replicate to the publishers so everything stays in sync.

Hope this helps