Book Image

Multi-Cloud Architecture and Governance

By : Jeroen Mulder
Book Image

Multi-Cloud Architecture and Governance

By: Jeroen Mulder

Overview of this book

Multi-cloud has emerged as one of the top cloud computing trends, with businesses wanting to reduce their reliance on only one vendor. But when organizations shift to multiple cloud services without a clear strategy, they may face certain difficulties, in terms of how to stay in control, how to keep all the different components secure, and how to execute the cross-cloud development of applications. This book combines best practices from different cloud adoption frameworks to help you find solutions to these problems. With step-by-step explanations of essential concepts and practical examples, you’ll begin by planning the foundation, creating the architecture, designing the governance model, and implementing tools, processes, and technologies to manage multi-cloud environments. You’ll then discover how to design workload environments using different cloud propositions, understand how to optimize the use of these cloud technologies, and automate and monitor the environments. As you advance, you’ll delve into multi-cloud governance, defining clear demarcation models and management processes. Finally, you’ll learn about managing identities in multi-cloud: who’s doing what, why, when, and where. By the end of this book, you’ll be able to create, implement, and manage multi-cloud architectures with confidence
Table of Contents (28 chapters)
1
Section 1 – Introduction to Architecture and Governance for Multi-Cloud Environments
7
Section 2 – Getting the Basics Right with BaseOps
12
Section 3 – Cost Control in Multi-Cloud with FinOps
17
Section 4 – Security Control in Multi-Cloud with SecOps
22
Section 5 – Structured Development on Multi-Cloud Environments with DevOps

Summary

This chapter was about the licensing of cloud platforms themselves and the software used within them. We have learned that there are different types of agreements for the usage of cloud services: purely consumption-based, commitment-based, and limited agreements, which are mainly used for trial periods.

We have seen that license agreements for software might change if we deploy software on cloud resources and that it might be worthwhile to implement SAM. Since licenses and contracts can become very complex, some companies decide to outsource the task of managing licenses to third-party brokers.

In the last section, we learned how we should set up enterprise enrollment in Azure, looked at organizations and accounts in AWS, and explored organizations, folders, and projects for the potential segmentation of billing in GCP. These enrollments come with a specific hierarchy that we need to deploy, but we have also seen that these hierarchical models in the main public clouds...