Best way to migrate from file datastore to S3 + BinaryLess Replication setup?
Dear community,
currently we have an AEM 6.5 deployment with the typical author, publisher instance seperation on AWS where each instance has their data store, segment store and node store on disk (EBS Volume).
The setup I want to move to is having the data store which takes up 95% of the crx-quickstart/repository directory migrated to S3 and then reduce the volume size significantly to achieve cost savings. The instances should also share this S3 bucket.
Our support team has set up the S3 connector as per documentation and migrated the data store, but seems to struggle with redeploying AEM on a fresh disk, installing necessary packages + code deployment and then reuse the state from the previous installation, but now with the data store offloaded.
I understand that it's easier to use this setup from the start, but there has to be a set by step approach to get to this point from on existing setup, right?
Would be very grateful for any high level steps on how to achieve this and remediate any potential issues or conflicts. How would we manage backup & restore in this scenario, as the backups are from the EBS disk but don't take into account the S3 bucket so things will get out of sync, right?
Regards,
ryg