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

Centralizing billing in multi-cloud

In the previous sections, we discussed the various billing and cost management options that Azure, AWS, and GCP offer. However, we're talking multi-cloud, so we might have workloads in at least two different clouds. If we want to know what our costs are, we will need to log in to multiple consoles to find out what our invoice will look like at the end of the month. We can do some exports to get it all consolidated in one spreadsheet, but that won't solve a couple of challenges.

First of all, in terms of financial reporting, the invoicing period should be the same. For example, in terms of the consolidation of cloud services from different providers, the invoicing period should be from the first day of the month until the last day of the month, so the 30th or 31st (February being an exception). Some services are billed from the 1st until the 1st of the next month. It might not seem an issue for an engineer, but in financial accounting...