We are starting to look at what it would take to move our entire GIS infrastructure to the cloud. This would include our enterprise geodatabases and Enterprise deployment.
I'm not terribly concerned about the Enterprise deployment part of the move. The portion that I'm really interested to hear peoples thoughts/ideas/experiences on is the actual data migration/setup/configuration/performance.
There are several logistical questions we have in order to fully understand what it would take on our end to provide our users with their familiar desktop setups if our enterprise databases were in the cloud.
I'm sure there are many things I've overlooked, we are mainly interested in getting our heads wrapped around the logistics of a move to the cloud.
Any thoughts/ideas/suggestions are welcome!
If snapshots / backups at the cloud level are a need, AWS will provide those for you where Azure doesn't have a way to do that. If you are storing data in a cloud database, you will want to have cloud desktop / jump machines otherwise the performance of reading / editing data will be degraded. Our desktop software connects to databases over IPs or machine hostnames, and if you have a domain setup in the cloud you can use OS auth from the desktop / jump machines.
A few follow-up questions (apologies in advance since we're new to this):
Again, thanks for any response. Does Esri have any videos/docs detailing install/setup/config in the cloud?
No worries, moving to cloud is not a small task!
I appreciate the help!
A few more follow-ups:
Thanks again!
I could only speak from my experience with Azure.
For databases, avoid Azure Database. Instead, try Azure SQL Managed Instance.
Also, in our experience, avoid Enterprise Cloud Builder.