Harvard University’s vision for enterprise architecture is to articulate and drive to common solutions, standards, and opportunities for alignment in order to reduce IT complexity and cost across the University and enable local innovation.
This document defines a basic set of data elements related to operational monitoring and instrumentation that should be provided by systems on-premises, in our AWS Cloud, or a SaaS provider.
A set of documents that define a Trust Model, describe what is currently in place, and a plan to move toward reducing complexity and the need for data sources to provision applications individually.
These Information Security Requirements apply to everyone at Harvard. They provide additional detail on how to be compliant with Policy and should be used as a normal part of daily life at Harvard in order to keep both Harvard confidential data and your own personal information secure.
This document describes the required metadata tags for Cloud Resources (e.g. instances, volumes, snapshots, managed databases, load balancers, distributed caching services) so that resources can be effectively leveraged across stakeholders.
This document presents a consolidated reference for consistent naming of Cloud Resources across all IT Organizations, which benefits the University in cost savings, automation and reduction of ambiguity.
This analysis of the architecture guidance on the number of production VPCs (Virtual Private Clouds) for services deployed in AWS examines four dimensions: Security, Cost, Operations, and Business Continuity and Disaster Recovery.
This document outlines potential problems associated with multiple applications running on a single instance, describes current best practices for isolating production applications, and makes recommendations to mitigate potential problems when best practices are not followed.
A set of principles that guide the selection of standards for APIs at Harvard and general development recommendations that impact effective interoperation of our systems and services.
This document outlines a mid-term future-state vision, strategy and design approach for directory services across the University to address overlapping services and data, inconsistent provisioning, and varying levels of support.
This document provides a series of guidelines for determining whether a Software as a Service (SaaS) solution should be established with a single shared subscription or multiple subscriptions.