Book Image

Hybrid Cloud for Architects

By : Alok Shrivastwa
Book Image

Hybrid Cloud for Architects

By: Alok Shrivastwa

Overview of this book

Hybrid cloud is currently the buzz word in the cloud world. Organizations are planning to adopt hybrid cloud strategy due to its advantages such as untested workloads, cloud-bursting, cloud service brokering and so on. This book will help you understand the dynamics, design principles, and deployment strategies of a Hybrid Cloud. You will start by understanding the concepts of hybrid cloud and the problems it solves as compared to a stand-alone public and private cloud. You will be delving into the different architecture and design of hybrid cloud. The book will then cover advanced concepts such as building a deployment pipeline, containerization strategy, and data storage mechanism. Next up, you will be able to deploy an external CMP to run a Hybrid cloud and integrate it with your OpenStack and AWS environments. You will also understand the strategy for designing a Hybrid Cloud using containerization and work with pre-built solutions like vCloud Air, VMware for AWS, and Azure Stack. Finally, the book will cover security and monitoring related best practices that will help you secure your cloud infrastructure. By the end of the book, you will be in a position to build a hybrid cloud strategy for your organization.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Software Hardware List
Packt Upsell
Contributors
Preface
Index

Identity and Access Management (IAM) 


The next underpinning service used is the Identity and Access Management Service. Traditionally, this meant having a common directory which the applications can query to authenticate end users. 

The IAM is normally a team effort between the system that can store and authenticate the users (the directory), and also provide the ability for us to tag the users and the application in some way. The application uses the tags in order to control the permissions for the user. The ability to fine-tune the authorization is called Role Based Access Control (RBAC). 

So, it can safely be assumed that the authentication is dependent on the directory. The authorization on the other hand is dependent on the application, which use the tags that are associated to the user or that the user is associated to. 

Note

In the case of Active Directory, the user is added to the "tag", in this case called the "Security Group" and in the application, we would define whether the user...