For the purposes of processing changed data, I would like to set up an asynchronous replica which has CDC enabled. The primary replica will not have CDC enabled to avoid any issues with CDC resource usage.
Change Data Capture and Other SQL Server Features states "[w]hen you use Always On, change enumeration should be done on the Secondary replication to reduce the disk load on the primary." When you look at Replication, change tracking, & change data capture - Always On availability groups it states "... CDC configuration is always performed on the current or intended primary replica."
From the Microsoft documents, it seems that the only way to enable CDC ONLY on the secondary database is to avoid Availability Groups and go with one of the more traditional replication options (i.e. Snapshot, Merge, or Transactional). Is that correct? Is there really no way of enabling CDC just on the secondary replica using Availability Groups even when the secondary replica is asychronous?