replication and different retention policies

Is it possible to have different retention times on replicated data?  I see a reference that says mtree replication is based on snapshots and so cannot have different retention times between replicated data.  However, I don't see a way to setup different retention policies on directory replication.  What we would like to have is 2 systems (one primary and one replication target) replicated with mtree replication with 30 days locally on each.  Then after 30 days use data-movement to send data to aws for long term retention and have the data expire on the replication target.  However, the replication target doesn't know data was sent to aws so it keeps it.  Primary maintains adequate free space while the replication target fills up with data older than 30 days.

Apologies if this was asked before, couldn't find it.  DDOS 6.0.2.20