Retool migration to new AWS account – license and configuration questions

Hey @summer

Thank you for reaching out to the Retool community. Let me address each of your questions below.

1. License Key — Using it on both environments during migration

Yes, this is fully supported. There is no limit to the number of separately deployed instances you can spin up with a single license key. Users are de-duplicated by email address, so running both environments simultaneously during your 1–2 day migration window will not affect your user count or licensing.

2. ENCRYPTION_KEY and JWT_SECRET

3. Additional considerations

  • Keep the same Retool version (3.52.3) on the new K8s deployment initially. This avoids introducing database migration changes during the infrastructure move. Upgrade after confirming the new environment is stable.

  • Keep the same PostgreSQL version on the new database to reduce the risk of unforeseen issues. You can upgrade PostgreSQL separately after the migration is validated.

  • Retool Database (if applicable): If you use Retool Database, it is separate from the platform database and requires its own migration and configuration via the RETOOLDB_POSTGRES_* environment variables.

  • Carry over all environment variables: Beyond ENCRYPTION_KEY and JWT_SECRET, ensure all other env vars from your Docker setup ( SSO, custom domains, cookie settings, source control, etc ) are replicated in your K8s Helm values.yaml or Kubernetes secrets.

Please let us know if you have any follow-up questions! I would be happy to help further.

Regards,
John | Retool Support

1 Like