ITS recently launched the AWS Cloud Migration project, which focuses on moving all major campus administrative systems away from on-premise hardware and to AWS Cloud. This move allows us to leverage the cloud's scalability and flexibility. UCSB will be able to improve disaster recovery posture, provide faster market access for IT customers, and improve UC sustainability goals by optimizing its infrastructure and decreasing the need for physical assets.
Migrating to AWS will creates campus data center capacity for faculty research computing and storage needs, while enhancing resiliency and cost transparency for our systems.
We're modernizing our capabilities and prioritizing the teaching, learning, and research goals of our community.
- We have to make decisions regarding the next generation of infrastructure as our existing gear ages beyond its life expectacy.
- UCSB can avoid upcoming capital improvements that would otherwise be required for its existing on-premise environment.
- The sooner the migration is completed, the quicker UCSB can begin to benefit from the operational improvements that AWS offers.
- Major administrative systems are moving to AWS infrastructure, with the migration covering ~900 VMs (Linux and Windows).
- IT infrastructure management will transition from an on-premise, capital-expense model to a cloud-based, OPEX model.
- Gain access to AWS's expansive cloud services, increasing its ability to innovate and scale
Project details
A list of systems moving to AWS Cloud has been compiled and divided into "waves" scheduled to be migrated on a specific date. Each wave will go through three phases:
- Intake
- Migration
- Hypercare
- Wave Phase Details: this document is a weekly overview of activities for each wave. Note that some waves will overlap with each other. If you have servers in multiple waves, you may be going through different phases (e.g. some of your servers will be going through intake, while others may be going through hypercare).
Additional resources
Server owners and app developers are encouraged to review the following (SSO required. You may need to request access to certain documents):
- Frequently Asked Questions
- Google drive: Each wave will have its own folder, with relevant documents and checklists
- Server Migration Schedule and Tracking
- Risk Log entry form
Please contact Project Manager Christopher Lee christopherlee116@ucsb.edu if you have any questions.
Wave Schedule