Establishing Enterprise Architecture on AWS
AWS Whitepaper

Enterprise Architecture Repository

An enterprise architecture repository is a collection of artifacts that describes an organization’s current and target IT landscape. The goal of the enterprise architecture repository is to reflect the organization’s inventory of technology, data, applications, and business artifacts and to show the relationships between these components.

Traditionally, in a non-cloud environment, organizations were restricted to choose expensive, off-the-shelf products to meet their enterprise architecture repository needs. You can avoid these expenses with AWS services.

AWS Tagging and Resource Groups let you organize your AWS landscape by applying tags at different levels of granularity. Tags allow you to label, collect, and organize resources and components within services.

The Tag Editor lets you manage tags across services and AWS Regions. Using this approach, you can globally manage all the application, business, data, and technology components of your target landscape.

A Resource Group is a collection of resources that share one or more tags. It can be used to create an enterprise architecture “view” of your IT landscape, consolidating AWS resources into a per-project (that is, the on-going programs that realize your target landscape), per-entity (that is, capabilities, roles, processes), and per-domain (that is, Business, Application, Data, Technology) view.

You can use AWS Config, Tagging, and Resource Groups to see exactly what cloud assets your company is using at any moment. These services make it easier to detect when a rogue server or shadow application appear in your target production landscape.

You may wish to continue using a traditional repository tool, perhaps due to existing licensing commitments or legacy processes. In this scenario, the enterprise repository can run natively on an EC2 instance and be maintained as before.