Simply put… it is moving your GIS from an on-premise environment onto a new, freshly built server environment in the cloud. A migration requires a lot of preparation and advance work, but it is worth the effort, resulting in cost savings and greater flexibility.
During this stage, we will work with your business to understand your current GIS estate and determine which Service(s), Database(s), and Third Party Applications are essential to meet your business needs. By the way… do you have a lot of old data or map services sitting idle? This is a great time to clean the closets and only take with you what you need! Once defined, ROK will architect a cloud environment specific to your organization's GIS and Security needs.
Anne Arundel County’s Commitment to Accelerate Digital Transformation This transformation commitment creates a more effective and efficient county government for employees, citizens, and communities. To effectively support every citizen of Anne Arundel County with the standardization, coordination, and dissemination of geographic information requires a GIS infrastructure that facilitates collaboration – and is both scalable and reliable. Power […]
The cloud-native deployment option for ArcGIS Enterprise, Kubernetes, is quite popular these days, but what is Kubernetes? K8s is entering the mainstream because of its scalability, resilience, and maintainability. While the deployment of ArcGIS Enterprise on Kubernetes is an exciting new frontier for IT architects, it’s still important for GIS end-users to understand what is […]
VDI has been and will continue to be a buzzword in the technology landscape, but what exactly is VDI? If you’ve heard of it, does it make you think of The Wizard of OZ – something magical, mysterious and hidden behind the curtain? Does it make you think of a keyfob code that never seemed […]
WHAT OUR CLIENTS HAVE TO SAY:
Migrating your GIS to AWS, Azure or any cloud solutions provider is accomplished in phases. Here is a brief overview of the methodology we use at ROK. Keep in mind that there are several steps within each phase, but this will give you an overview of what needs to take place.
Phase I: Spin up and configure the cloud environment you will use to support your software. Apply security, backup and retention policies.
Phase II: Install and configure your Esri Software. Deploy Virtual Desktop Instances.
Phase III: Migrate your GIS ... this is a great opportunity to “clean the closets” and ensure you are only migrating what you need. We generally start migration planning in Phase I.
Phase IV: Cut Over to your new Cloud GIS environment. The entire process timeline varies depending on the complexity of your environment. As a very general rule you should budget 8-10 weeks.
There will always be challenges to overcome when encountering something different or unknown. If some of your data or technology is proprietary, you may not legally be able to deploy to the cloud. You may need to modify and/or map your application design and architecture to follow the cloud architecture. You could experience downtime due to technical outages (loss of power, maintenance, etc), but this would also be true on-premise.
This really depends on the Esri software that is in use. You can find the specifications on Esri's website. Here is a link to get you started: ArcGIS Server 10.8 system requirements—ArcGIS Enterprise system requirements | Documentation
Deploying and managing a 3-tier environment in the cloud is standard practice for many of the organizations we serve. Migration, when planned correctly can be a smooth and painless experience.
When working with clients on Cloud Migrations, the first step is to understand their environment. To do this, we start with a holistic view, formulating a detailed plan that serves as a roadmap. Using this roadmap, we work with the client to transfer and configure data (Database(s), Imagery, Flat Files etc.), working/project files (ArcMap/Pro documents, scripts, proprietary information), web applications and any third party integrations. After all configurations are complete, we validate the Cloud Environment through a client testing and QA/QC Phase to work out any and all issues. We then hand the keys over and GO LIVE!
Latency, not to be confused with bandwidth, is a known factor since distance is key to determining latency - no matter how fast a connection, data must still physically travel the distance from cloud to machine and is constrained by the laws of physics 🙂 With this in mind, we can reduce the travel time by staying in one availability zone. Most of the clients we work with actually realize better performance after migrating to the cloud.