Bumped on the shared file system service provided by AWS which they call as Elastic File System (EFS). EFS is more like a file system in a network mounted on multiple compute (EC2) instances. All the compute instances can read and write to it as EFS supports read-after-write consistency.
Wondering how this could be useful to Content Management Systems (CMS) systems such as Adobe Experience Manager (AEM). This type of CMS systems persist the content in the local disk itself and hence scaling out is a challenge.
- EFS can be used as shared binary data store. Author and publish instances could use the same data store.
- AEM dispatcher can use EFS for storing cached files. This allows sharing cache store across dispatchers.
- Can EFS be used to scale out TarMK based AEM author instances? Multiple EC2 nodes could mount the same filesystem which has the tar segment files? I doubt as TarMK implementation is based on memory mapped files.
BTW, EFS is stuck in preview for over 6 months. There are alternatives such as ObjectiveFS out there.
References