We plan to migrate our self-hosted retool solution from our current infrastructure to AWS.
We check that you have two solutions for AWS, and I would like to ask you a couple of questions:
You have two solutions in AWS for a self-hosted solution. Could we migrate to any of them?
Could we have a temporally key for the migration? Other solutions that you can propose to us?
How can we migrate our current dashboards to the new environment in AWS?
Hi @Dario,
I would love to help but I would need more background information on your current self-hosted set up 
Hypothetically yes you should be able to migrate to either of them. But I am not sure what features or deployment setups you are currently using that would be limited in any way or require additional configuration to achieve full parity.
I do not believe we have a temporary key, that may be an option for enterprise plan users but I would direct anyone looking to make migrations of large orgs to their Technical Account Manager.
Can you give me more details on your 'current dashboards' are these dashboards built inside of Retool apps? Check out our docs as we have resources for how to complete self-deployment on AWS Fargate and ECS, choosing to use Terraform or CloudFormation will depend on what you are currently using and which tool best suites your needs for infrastructure.
Hello @Jack_T ,
We have installed the self-hosted version of retool on our own server and now, we are moving all our infrastructure to AWS.
My only concern is how I can migrate all the boards from the old self-hosted to the new one?
Is it as easy as "export as json" and after import it?
How can we manage the keys? I mean, can a run the same key in old and new environments at the same time? Or do I have to export everything to our local machines, add the new key to the new environment and import everything?
Kind regards!!!
Hi @Dario,
More of less that is the process, export apps as JSON and then import them in.
Only issue would be if you are also updating versions. Where there would be a chance that some part of the app that has changed causes a surprise on import.
Not sure which keys you are referring to, if you have api keys then you would need to follow the security policy. Some APIs will see that the same key is being used from different IP addresses for example and suspect a malicious actor.
I would imagine that once you spin up the deployment on your local machine, you would need to import everything and add the keys. But this is outside of the scope of what the community support will cover. There may be other users going through this process who can give advice.
Hello @Jack_T ,
Yes, I am referring to the API keys. I would like to avoid problems while we are migrating from the old to the new one. Because, as you mentioned, is it possible that during some days you will detect that may be, our API key may come from two different places.
Thank you for your answer!