This summer, we are transitioning report rendering (FOP) from local servers to a centralized service hosted by Amazon Web Services (AWS). This transition will start in April 2025 and should be completed by July 2025.
NOTE: This change will not impact any reports written in SSRS.
What's Improving?
- Moving report rendering to a centralized service will free up local server resources, improving performance for other tasks.
- This will also streamline maintenance, allowing districts to receive report rendering improvements without taking Campus SIS release updates.
- District data remains secure and protected. All data transmitted between Campus sites and AWS will be encrypted using industry-standard encryption protocols, both in transit and when stored centrally with AWS.
The implementation of this change will come in three phases.
- Phase one is targeted to begin with the April release; Campus.2515. Report rendering for non-batch FOP reports will occur both locally and centrally. The local report is displayed if central rendering fails.
- Phase two is targeted to begin with the May release; Campus 2519. Report rendering for all FOP reports (both non-batch and batch) will occur both locally and through AWS. The local report is displayed if central rendering fails.
- Phase three will begin with the July release; Campus 2531. Report rendering for all FOP reports will only occur centrally. Local server resources will no longer be used for FOP report rendering.
