22-09 - Migrate Hetzner Provisioned Instances to AWS

The aim here is to close Hetzner instances and move them to AWS. This is, however, a breaking change, so all integrations must be migrated manually.

Limitations of Hetzner Instances

• Cannot upgrade to IM 3.0 and higher

• No longer supported old versions of Hetzner

Process

There are two scenarios:

• Integration is empty (no routes, mappers, etc.):

  1. Write down the name of the user in the Monitoring tab.

  2. Delete the instance.

  3. Create an instance with the same name.

  4. Enter this user back into the Monitoring tab of a new instance.

• Integration has active entities:

  1. Create a new instance with a different name on the latest version.

  2. Copy the monitoring user from the old instance to the new one.

  3. Copy routes, mappers and other entities.

  4. If the integration is DOWN, connections and filters must be retrieved manually from the server – get it from respective folders and upload it to Git.

  5. Deploy all above listed entities.

  6. Check the log that everything works.

Status