Skip to content

Migrating from Heroku to AWS

connorshea edited this page Jan 29, 2016 · 1 revision

Notes:

Problems:

  • We've monkey-patched the asset pipeline for Heroku in places, so moving to AWS might break that.
  • No Heroku Pipelines, so Staging environments are harder to make happen.
  • No automated database backups, we'd have to set that up ourselves (I think?).
  • SendGrid (or another email provider we'd switch to) has to be paid for if we use AWS, currently Heroku lets us use it for free despite SendGrid's Pricing page saying you only get 45 days.
  • Setting up integration with GitHub is harder, no built-in GUI for pushing changes. We'd probably have to use AWS CodePipeline.
  • We'll have to pay for our own SSL certificate.
  • Memcachier

Clone this wiki locally