Deploying ArcGIS Applications in the AWS Cloud
Five years ago one of North America’s largest full service geospatial solutions company that specialized in multi-disciplinary geospatial data generation, integration, enablement, and analytics delivered through a unique cloud-based infrastructure, began deploying customer-facing applications based on ArcGIS at the Amazon Web Services (AWS) cloud. The company uses ArcGIS desktop to build maps, merge imagery and vector line work, then used ArcGIS to publish it to ArcGIS Online as well as to AWS.
Spatial Data is Too Storage Intensive for AWS Alone
To get around EBS restrictions, the company briefly tried an open source-based storage approach, which only added to management complexity and required additional capacity and AWS instances – hence additional costs. In exploring options, the company also learned that using products like Gluster with EBS storage didn’t avoid the issue of single EC2 access either.
Deploying AWS Compute with Zadara Storage
The Nitty-Gritty of the Storage Architecture
With this approach, they had the best of all worlds –highly reliable enterprise-grade storage with features not available from AWS, the full geographic data management power of ArcGIS, and a storage architecture that was far more flexible and scalable.
Assuring Client Demands with Disaster Recovery and High Availability
Most technologies come with all kinds of gotcha’s, yet the team found our approach to genuinely work as advertised: as a flexible, scalable approach to running a client-facing ArcGIS data storage application in the public cloud. It saved time, management complexity and costs, while meeting client needs for Web access, and providing a framework for further growth with client-facing offerings.
More importantly, because the deployment was painless, they could stay focused on its core mission of serving smart geospatial information to clients, and spend less time addressing the details of maintaining an enterprise cloud solution.