AWS resources after Heroku

Owned by Eddie Rubeiz
Last updated: Jul 26, 2021
1 min read

A few days after switching 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 boxes. Do not delete them yet: a) we can still switch back to them in the event of a major problem, and b) they’re a handy reference in the short term.

After 4 - 8 weeks

  • Remove

    • All the scihist_digicoll boxes. Permanently.

    • The elastic IP addresses digicoll-staging and digicoll-production

    • All volumes that are not in-use

    • All unused snapshots

  • Keep

    • ArchivesSpace boxes

  • Review

    • Reserved instances (work with Chuck and Vince on this)

    • Security groups. We can probably get rid of:

      • internal-networking-production

      • internal-networking-staging

      • CHF-Access-Web

      • Temp-Development

      • Temp-Staging

      • Temp-Production

See also: Ansible post-heroku.