Post-Heroku timeline

Short term

In the week or so after moving to Heroku:

Save the final config/local_env.rb files for staging and prod to a secure area on the P drive, for short-term reference.
Stop all the scihist_digicoll s3 instances. Do not delete them yet:
- we can still switch back to them in the event of a major problem
- we want them on hand for reference in the short term.
Remove all snapshots
Make a serious attempt to get Ansible archivesspace build working from anywhere other than the Management server (see below).
Remove Voices in Biotech code from Ansible.
Continue to resolve post-launch problems with Heroku.

Once Heroku has been stable for 4 to 6 weeks:

Remove
- All the scihist_digicoll boxes (yes, actually terminate the ec2 instances).
- local_env.rb files.
- The elastic IP addresses digicoll-staging and digicoll-production
- All volumes that are not in use
- Management server (if Ansible archivesspace build works.)
- Playbooks and roles from Ansible. Which ones can be removed depends on whether we can run Ansible from our dev machines.)
Keep
- ArchivesSpace servers - staging and prod.
Review, in collaboration with Chuck and Vince
- Reserved instances
- Security groups.

Once Sarah Newhouse is settled, she should convene ArchivesSpace stakeholders to plan the future of the server and its functions.
Attempt issue #1043 - explore Terraform (or even a rake task or shell script) instead of Ansible to maintain our s3 configuration.

More about aws, ArchivesSpace and Ansible after Heroku.