Not supported on Cloud Service

Replication agents and Sling Content Distribution on AEM Cloud Service

Cloud Service publishes content through Sling Content Distribution, managed by Adobe. Replication agent configurations, custom transport handlers and reverse replication have no equivalent. The Replication API still exists for triggering publication, but it cannot replicate packages larger than 10 MB.

What to use instead

Manage Publication or the Tree Activation workflow step for authors; Replicator API calls for code; event-driven integrations for anything that used a custom agent to push content elsewhere.

How to fix it

1. Inventory agents under /etc/replication and note any that target non-AEM systems.
2. Remove agent definitions from packages.
3. Rebuild custom transports as integrations triggered by Sling Jobs or Adobe I/O events.
4. Replace dispatcher flush agents with CDN and dispatcher cache rules.

How we detect it

• Readiness scan rule replication-agent-ext: Custom replication transport or content builder.
• Readiness scan rule replication-agent-config: Replication agent configuration in the repository.

Best Practices Analyzer reports it under REP.

Can agents fix it?

High for removing agents; low for rebuilding custom transports.

Source: Adobe Experience League. Checked 19 October 2026.