Confluence deployment with server license with EFS as shared file system on AWS

Brute Force

I am trying to deploy confluence with a server license. I have created an autoscaling group so that if the ec2 instance is down due to some reason, a new instance will be automatically spawned in one of the two availability zones. I know I cannot have more than one instance running as I have a server license. Now given some context, my question is how can I use efs so that if the ec2 instance is down I will not lose data and the new instance can pick off from where the old one left off. By comparing Atlassian's standard data center hosting, I can see they are only storing shared-home and attachments in efs. Can I do the same with a server license? Or is there any other approach? Thanks in advance

Nic Brough -Adaptavist-

Apologies for the delay, but yes, you can do this, in later versions.

Server now has the same directory structure as DC and the directories for shared-home and attachments contain stuff that is fine to keep on shared storage (attachments have always been suitable for sharing).  Do not put the other directories on shared storage though, it will cause you problems.

Given the shared storage and a cold or warm (Warm meaning the server is up and Confluence installed and configured, but not running), then the shared storage gives you a fast reponse to a failure - all you need to do is ensure the main service really is dead, then change the network such that people will be pointed to the standby, start the standby and trigger a full re-index.

Note that I'm assuming the primary database is either still running ok, or is under full replication to a secondary copy that the stanby Confluence is looking at (you'll need to stop replication and make the replica read/write)