![]() ![]() Images are saved in the same EFS for each environment – however, they would not appear in Drupal until an administrator initiated a database import from the environment. In the event of autoscaling, failure or termination to the instance, a new web server would automatically boot with EFS attached, linked to the files folder to serve web images. The public and private file system for each environment was stored in Amazon EFS, where a mount script would automatically attach a filesystem to all images and documents. ![]() RDS eliminated the need for Ohlone to perform many database administrative tasks (e.g. Daily backups of the databases also allowed for point-in-time restore if needed. The database for each environment was stored in Amazon RDS, another managed service from AWS that ensures databases are updated and maintained while sustaining a secure connection to the web servers. It is a leading-edge example of using automation tools to follow DevOps best practices and will help to ensure that Ohlone’s web servers are highly available, secure and automatically updated with the latest application code following Continuous Integration/Continuous Deployment (CI/CD) techniques. When the IT team pushes changes to a specific branch, Amazon CodePipeline identifies the change and updates the Elastic Beanstalk environment. Each Elastic Beanstalk environment was connected to the corresponding branch (Master, Staging, and Dev) in Amazon CodeCommit via Amazon CodePipeline. We chose the AWS Elastic Beanstalk service to lower the administrative burden on the Ohlone staff, since Elastic Beanstalk is a self-managed Platform as a Service architecture that implements the application release process into AWS architecture. This design included an application deployment for their sophisticated Drupal application, which was maintained in an Amazon CodeCommit repository.Īfter engaging with Ohlone’s IT team, our DevOps team created three Elastic Beanstalk environments for the client: Production, Staging, and Development. InterVision constructed a cloud architecture strategy using our prescriptive Cloud Migration Lifecycle Assurance (CMLA) program that documented recommendations such as the architectural buildout in AWS and the strategy to migrate applications and websites after the AWS infrastructure had been developed and deployed. Ohlone College engaged with InterVision to plan and develop their cloud architecture environment, and to migrate their primary Drupal website to the AWS cloud. Moving Ohlone’s website to the cloud supported the long-term direction of the institution and would help to empower future strategies. Their Drupal website needed to be migrated from an on-premise environment to the cloud, so that users could gain greater accessibility to online resources. Ohlone College desired to be fully operational in the cloud and needed assistance in developing their cloud environment. With more than 16,000 students annually, the college also has campuses in Fremont, Newark and online. ![]() Ohlone Community College is a multi-campus community college located in the San Francisco Bay area of California. Communications and Contact Center ConsultingĭRUPAL WEBSITE MIGRATION TO AWS: OHLONE COLLEGE.Business Continuity and Disaster Recovery. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |