Cloudera Docs

Configuring Access to Azure on Cloudera Private Cloud Base

You can use Shared Key, Managed Instance, Shared Access Signature, and so on to configure access credentials to authorise access to Azure containers. For example, a shared key account can be configured for use regardless of which account is accessed with the property fs.azure.account.key or you can configure an identity to be used only for a specific storage account with fs.azure.account.key.<BUCKET NAME>.blob.core.windows.net.

After you create a storage account, Azure generates two 512-bit storage account access keys. You can use these keys to authorize access to data in your storage account. For information on how to access this Shared Key, see View account access keys. To configure access to the Azure container, add the Shared Key details in the core-site.xml file using Cloudera Manager.
  1. In Cloudera Manager, select Clusters > HDFS service.
  2. Click the Configuration tab.
  3. Search for core-site.
  4. In the Cluster-wide Advanced Configuration Snippet (Safety Valve) for core-site.xml option, click the + sign and add the below properties: 
    Name: fs.azure.account.auth.type.<account_name>.dfs.core.windows.net 
Value: SharedKey (or any other auth type such as OAuth or SAS)
            
Name:fs.azure.account.key.<your_storage_account_name>.dfs.core.windows.net
Value: <access_key>
  5. Click Save Changes.
  6. Next to the HDFS title, click ig> Restart and Redeploy to restart and redeploy the configurations.