The system was originally developed to run using on-premise hardware, purchased in the early stages of the project. This hardware would serve as the development platform as well as to provide an Initial Operating Capability (IOC) during the first few years of the project. While the hardware proved adequate for running three fire simulations at once (a contract requirement), most of the time the system was relatively idle due to the seasonal aspect of wildfires. In addition, during peak fire season there was no way to add temporary computing capability to handle those peaks in a cost-effective manner.
During the last two years, work was undertaken to port the system to a cloud vendor, specifically Amazon Web Services (AWS). The system was split into always-running and on-demand components. Always-running components include a host to ingest High Resolution Rapid Refresh (HRRR) data for the WRF-Fire boundary conditions, and an ArcGIS server to provide fire behavior and weather products to users. The WRF-Fire component was modified to run using on-demand compute resources, provisioned as needed when a user requested a simulation. The new cloud-based configuration has many benefits, including better resource utilization, almost unlimited scalability during peak season, and easy upgrade to more powerful compute resources as AWS makes them available in production.