Book Image

Realize Enterprise Architecture with AWS and SAFe

By : Rajnish Harjika
Book Image

Realize Enterprise Architecture with AWS and SAFe

By: Rajnish Harjika

Overview of this book

Agile implementation of enterprise architecture (EA) in the cloud is a powerful organizational tool, but it is challenging, particularly for architects who are used to on-premises environments. This in-depth guide will tell you all you need to know to reap the benefits of applying EA in your organization to achieve operational efficiency. Starting with an overview of the foundations of enterprise architecture, you'll see how it can be applied to AWS as well as explore the frameworks AWS provides for EA, such as the AWS Well-Architected Framework. That's not all – the book shows you how these frameworks align with The Open Group Architecture Framework (TOGAF) architecture development method (ADM) and the Zachman Framework so that you can choose the right fit for your organization. As you advance, you'll learn how to apply SAFe to make your organization agile as well as efficient. Once you've gotten to grips with the theory, you can explore use cases and take a quiz at the end of the book to test yourself and see how EA is applied in practice. By the end of this enterprise architecture book, you'll have the skills and knowledge required to apply EA in the cloud with AWS and drive your organization to become super-efficient and agile.
Table of Contents (17 chapters)
1
Part 1 – Enterprise Architecture Foundation and Implementation
5
Part 2 – Enterprise Architecture Frameworks
9
Part 3 – SAFe in EA and the Cloud
12
Part 4 – Setting Up an EA

Guidelines for a successful migration

In this section, there are guidelines that are divided into multiple parts to help you plan your migration and to conduct migration sprints.

Planning

In order to migrate resources to AWS, you must figure out how you will migrate them, the tools you will use, and the operating model you will use to maintain, govern, and secure them. Prepare for the migration by following these best practices:

  • Identify the key assumptions for a comprehensive wave plan. The number, dependencies, and tools used in each sprint, along with the owner of each sprint, should be identified.
  • Integrate account structures, security, networking, automation, and pipelines.
  • Preparing the landing zone is essential.
  • The migration tools must be selected and obtained.
  • Define the processes for change management and impact assessment.
  • Decide how you will communicate.
  • Establish the production processes and operating models.
  • Resources, including...