Multi-Cloud Tenant Database

⭐️🏢 CoreA central database provides information about tenants in different clouds using a unified information schema. Tenants can be registered in this database via an API or are stored there by combining different tenant lists/exports into a common database schema (ETL).

Organizations embarking on their cloud journey often start implementing dedicated processes for Tenant Provisioning and maintaining a dedicated Cloud Tenant Database for each individual cloud platform. As the organization’s cloud strategy evolves towards embracing a multi-cloud approach, individual cloud platform silos make it difficult to establish visibility over the organization’s multi-cloud adoption.

Furthermore, maintaining different tenant databases per platform leads to inconsistent metadata about your cloud tenants. This makes it difficult to establish a consistent level of governance across multiple cloud providers and platform technologies. There is also a lot of redundant effort for data integration with each platform’s cloud tenant database, especially when considering capabilities like Link Cloud Tenants to CMDB/EAM or Multi-Cloud Tagging Policy.

Best Practices for Establishing Multi-Cloud Visibility with a Cloud Tenant Database

To successfully implement a multi-cloud tenant database, it needs to serve as a Cloud Tenant Database for each platform. Review that building block for considerations and best practices of building a cloud tenant database. This building block focuses on the considerations to establish a consistent multi-cloud database.

Align and Centralize Requirements

If your organization has historically managed cloud platforms as separate silos, chances are high that platform teams have implemented processes like Tenant Provisioning, Tenant Deprovisioning / Decommissioning or Cloud Tenant Tagging individually. When building a multi-cloud tenant database, you will also have to consider how to align these processes across clouds so they can be integrated with a single multi-cloud tenant database. A natural next step in this process could be implementing the building block Multi-cloud tenant database integrated with lifecycle management.

Creating this alignment between different platform implementations and functional stakeholders (IAM, Compliance, Finance) can be challenging. Establishing a Cloud Foundation team empowered with a clear-cut mission is the best approach to overcome these challenges.

Start your Multi-Cloud Journey

Implementing a multi-cloud strategy has its pitfalls. Read these 6 tips to start your multi-cloud journey.

Start your Cloud Journey

Consider Collaborative Approaches to Maintaining Tenant Metadata

Maintaining tenant data at scale is a lot of work. Even more so than with a platform-specific Cloud Tenant Database, enabling collaboration between different stakeholders is the key to maintaining a high-quality information repository about cloud tenants. The building block Self-Service Multi-Cloud Tenant Database covers implementing this in more detail.

Maintain a Cloud Service Register to Meet Regulatory Requirements

Industry-specific regulation can require your organization to maintain a register of all cloud outsourcing activities. A multi-cloud tenant database can help meet these requirements. One example of this is the “Cloud Service Register” in the financial industry as recommended by the European Banking Authority’s Recommendations on Cloud Outsourcingopen in new window.

Last Updated: