Migrate from Heroku to AWS
Click the Deploy with Microtica button below and follow the template steps to migrate your existing Heroku application to your AWS account.
This is a step-by-step tutorial on how to migrate your existing project from Heroku to AWS, using Microtica’s ready-made infrastructure and application templates. This guide applies to developers that have a running application on Heroku with PostgreSQL or MySQL database and covers:
- Setup of infrastructure on AWS
- Importing your existing application
- Migrating PostgreSQL/MySQL database from Heroku to AWS
If you want to deploy a new application on AWS, here is a guide on How to create an application from a template.
You can provision a complete Kubernetes cloud infrastructure through Microtica, or you can connect your existing Kubernetes cluster running on basically any cloud provider or on-premise.
Microtica K8s is fully integrated with Microtica pipelines so you can easily define your automation to build, test and deploy services on Kubernetes in one place.
To create a Kubernetes infrastructure on your AWS account follow the complete guide below:
Amazon EKS
A step-by-step guide on how to create a Kubernetes cluster on your AWS account.
2. Import your existing app
Using our templates you can import any application you already have on your Git account. We support all the popular Git providers, like GitHub, GitLab, Bitbucket, and CodeCommit. Import your repository, select a cluster and deploy your app. Follow the tutorial below:
Import an existing application
A step-by-step guide on how to import your existing application and deploy it on AWS.
To export the data from your Heroku Postgres database, create a new backup and download it, using the following commands:
To export the data from your Heroku MySQL database, dump the Heroku database on your local development environment using mysqldump tool.
If you get this error message "Unknown table 'COLUMN_STATISTICS' in information_schema", add the command --column-statistics=0. The command adds ANALYZE TABLE statements to the output to generate histogram statistics for dumped tables when the dump file is reloaded.
If you get this error message "Access denied; you need (at least one of) the PROCESS privilege(s) for this operation", add the command --no-tablespaces. The suppresses all CREATE LOGFILE GROUP and CREATE TABLESPACE statements in the output of mysqldump.
To establish a connection between your local development environment and AWS please follow the Access the RDS database guide.
Once the connection is established, you can proceed with moving the local copy of the data to AWS.
Load the dump into your Amazon RDS PostgreSQL using the pg_restore tool.
