Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Multi-Cloud Strategy for Cloud Architects - Second Edition

You're reading from  Multi-Cloud Strategy for Cloud Architects - Second Edition

Product type Book
Published in Apr 2023
Publisher Packt
ISBN-13 9781804616734
Pages 470 pages
Edition 2nd Edition
Languages
Author (1):
Jeroen Mulder Jeroen Mulder
Profile icon Jeroen Mulder

Table of Contents (23) Chapters

Preface 1. Introduction to Multi-Cloud 2. Collecting Business Requirements 3. Starting the Multi-Cloud Journey 4. Service Designs for Multi-Cloud 5. Managing the Enterprise Cloud Architecture 6. Controlling the Foundation Using Well-Architected Frameworks 7. Designing Applications for Multi-Cloud 8. Creating a Foundation for Data Platforms 9. Creating a Foundation for IoT 10. Managing Costs with FinOps 11. Maturing FinOps 12. Cost Modeling in the Cloud 13. Implementing DevSecOps 14. Defining Security Policies 15. Implementing Identity and Access Management 16. Defining Security Policies for Data 17. Implementing and Integrating Security Monitoring 18. Developing for Multi-Cloud with DevOps and DevSecOps 19. Introducing AIOps and GreenOps in Multi-Cloud 20. Conclusion: The Future of Multi-Cloud 21. Other Books You May Enjoy
22. Index

Understanding the need for demarcation

Typically, when we talk about demarcation in cloud models, we refer to the matrix or delineation of responsibility: who's responsible for what in IaaS, PaaS, and SaaS computing? The following diagram shows the very basics of this matrix:

Figure 6.6 – Demarcation model in cloud deployment

However, we need a much more granular model in multi-cloud. We have been discussing policies throughout this chapter and by now, we should have concluded that it's not very easy to draw some very sharp lines when it comes to responsibilities in our multi-cloud environment. Just look at the solution stack – even in SaaS solutions, there might be certain security and/or compliancy policies that the solution needs to adhere to. Even something such as an operating system might already be causing issues in terms of hardening: are monitoring agents from a PaaS provider allowed or not? Can we run them alongside our preferred monitoring solution...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}