Managed identities

You must create one managed identity.

The IDBroker component of Cloudera uses user-assigned managed identities for controlling access to ADLS Gen2 and stores and manages the mappings between the services/users and the corresponding managed identities. The following managed identity must be created.

Table 1. Managed identities
Managed identity Description Steps

Logger (Required)

This managed identity is used by Cloudera to write telemetry logs and backups.

  1. Create a managed identity.
  2. Assign Storage Blob Data Contributor role to this managed identity on the scope of the Logs Location Base and Backup Location Base (if created) created for Cloudera.

The following diagram illustrates the minimal required setup where Backup Location Base is in the same location as the Logs Location Base:

Figure 1. Minimal required setup if Backup Location Base matches Logs Location Base
Flowchart indicating Logger connected to Storage Blob Data Contributor connected to $(LOGS_LOCATION_BASE) container

The following diagram illustrates the minimal required setup where Backup Location Base and Logs Location Base are separate:

Figure 2. Minimal required setup if Backup Location Base and Logs Location Base are separate
Flowchart indicating Logger connected to Storage Blob Data Contributor connected to $(LOGS_LOCATION_BASE) container and $(BACKUP_LOCATION_BASE) container