...
A ) Move the ArchivesSpace software to a hosted provider.
As part of this, we may also wish to (or have to) update the version of ArchivesSpace.
We may also decide, as part of this work, to turn on the public user interface.
If we turn on the PUI, the HTML finding aids become obsolete.
B ) Run the export scripts from a hosted environment. It may be possible to run them from a serverless environment, such as AWS lambda.
C ) Replace Apache with an S3 bucket.
Notes
It may also be possible to get a hosted ArchivesSpace to serve the EADs directly. If so, it may be possible to If an ArchivesSpace hosting provider, as part of their service, can take care of exporting and serving the EADs, we can avoid doing B ) and C ) altogether.
Because the ArchivesSpace server is the only one left that we use Ansible for, each of these steps has the side-effect of cutting out big chunks of our Ansible code. For instance, C) should allow us to get rid of all our Apache-related code in Ansible.
A ), B ) and C ) above could be treated as independent projects and be done in any order.
...