Register an Azure environment from CDP UI

Once you’ve met the Azure cloud provider requirements, register your Azure environment.

Before you begin

This assumes that you have already fulfilled the environment prerequisites described in Azure requirements.

Required role: EnvironmentCreator

Steps

  1. Navigate to the Management Console > Environments > Register environment:
  2. On the Register Environment page, provide the following information:
    Parameter Description
    General Information
    Environment Name Enter a name for your environment. The name:
    • Must be between 5 and 28 characters long.
    • Can only include lowercase letters, numbers, and hyphens.
    • Must start with a lowercase letter.
    Description (Optional) Enter a description for your environment.
    Select Cloud Provider Select Azure.
    Microsoft Azure Credential
    Select Credential Select an existing credential or select Create new credential.

    For instructions on how to create a credential, refer to Create an app-based credential.

  3. Click Next.
  4. On the Data Access and Data Lake Scaling page, provide the following information:
    Parameter Description
    Data Lake Settings
    Data Lake Cluster Name Enter a name for the Data Lake cluster that will be created for this environment. The name:
    • Must be between 5 and 100 characters long
    • Must contain lowercase letters
    • Cannot contain uppercase letters
    • Must start with a letter
    • Can only include the following accepted characters are: a-z, 0-9, -.
    Data Lake Version Select Cloudera Runtime version that should be deployed for your Data Lake. The latest stable version is used by default. All Data Hub clusters provisioned within this Data Lake will be using the same Runtime version.
    Data Access and Audit
    Assumer Identity Select the Assumer Identity managed identity created in Minimal setup for cloud storage.
    Storage Location Base Provide the ADLS Gen2 location created for data storage in Minimal setup for cloud storage.
    Data Access Identity Select the Data Lake Admin Identity managed identity created in Minimal setup for cloud storage.
    Ranger Audit Identity Select the Ranger Audit Identity managed identity created in Minimal setup for cloud storage.
    IDBroker Mappings We recommend that you leave this out and set it up after registering your environment as part of Onboarding CDP users and groups for cloud storage.  
    Scale
    Scale Select Data Lake scale. By default, “Light Duty” is used.

    For more information on data lake scale, refer to Data Lake scale.

  5. Click Next.
  6. On the Region, Networking and Security page, provide the following information:
    Parameter Description
    Region
    Select Region Select the region that you would like to use for accessing and provisioning resources from CDP.

    If you would like to use a specific existing virtual network, the virtual network must be located in the selected region.

    Resource Group
    Select Resource Group You have two options:
    • Select one existing resource group. If you select this, all CDP resources will be provisi0oned into that resource group.
    • Select Create new resource groups to have CDP create multiple resource groups.
    Network
    Select VNet You have two options:
    • Select the existing virtual network where you would like to provision all CDP resources. Refer to VNet and subnets.
    • Select Create new network to have a new network with three subnets created.
    Select Subnets This option is only available if you choose to use an existing network. Multiple subnets must be selected and CDP distributes resources evenly within the subnets.
    Network CIDR This option is only available if you select to create a new network.

    If you selected to create a new network, provide Network CIDR that determines the range of private IPs that VMs will use. This must be a valid private IP CIDR IP in IPv4 range.

    For example 10.10.0.0/16 are valid IPs. /16 is required to allow for enough IP addresses.

    Create Private Subnets This option is only available if you select to have a new network and subnets created. Is is turned on by default so that private subnets are created in addition to public subnets. If you disable it, only public subnets will be created.
    Enable Cluster Connectivity Manager This option is enabled by default. You can disable it if you do not want to use CCM. You can use Cluster Connectivity Manager (CCM) for communication with Data Lake and Data Hub workload clusters that are on private subnets. For more information about the required setup, refer to Cluster Connectivity Manager documentation.
    Create Private Endpoint By default, the PostgreSQL Azure database provisioned for your Data Lake is reachable via a service endpoint (public IP address). To increase security, you can optionally select to have it reachable via a private endpoint instead of a service endpoint.
    Create Public IPs This option is disabled by default when CCM is enabled and enabled by default when CCM is disabled.
    Proxies
    Select Proxy Configuration Select a proxy configuration if previously registered. For more information refer to Setting up a proxy server.
    Security Access Settings
    Select Security Access Type This determines inbound security group settings that allow connections to the Data Lake and Data Hub clusters from your organization’s computers. You have two options:
    • Create new security groups - Allows you to provide custom CIDR IP range for all new security groups that will be created for the Data Lake and Data Hub clusters so that users from your organization can access cluster UIs and SSH to the nodes.

      This must be a valid CIDR IP in IPv4 range. For example: 192.168.27.0/24 allows access from 192.168.27.0 through 192.168.27.255. You can specify multiple CIDR IP ranges separated with a comma. For example: 192.168.27.0/24,192.168.28.0/24.

      If you use this setting, several security groups will get created: one for each Data Lake host group the Data Lake and one for each host group), one for each FreeIPA host group, and one for RDS; Furthermore, the security group settings specified will be automatically used for Data Hub, Data Warehouse, and Machine Learning clusters created as part of the environment.

    • Provide existing security groups (Only available for an existing VPC) - Allows you to select two existing security groups, one for Knox-installed nodes and another for all other nodes. If you select this option, refer to Security groups to ensure that you open all ports required for your users to access environment resources.
    SSH Settings
    New or existing SSH public key Upload a public key directly from your computer.
    Add tags You can optionally add tags to be created for your resources on Azure. Refer to Defining custom tags.
  7. Click Next.
  8. On the Storage page, provide the following information:
    Parameter Description
    Logs
    Logger Identity Select the Logger Identity managed identity created in Minimal setup for cloud storage.
    Logs Location Base Provide the ADLS Gen2 location created for log storage in Minimal setup for cloud storage.
    Backup Location Base (Optional) Provide the ADLS Gen2 location created for FreeIPA backups in Minimal setup for cloud storage. If not provided, the default Backup Location Base uses the Logs Location Base.
    Telemetry
    Enable Workload Analytics Enables Workload Manager support for workload clusters created within this environment. When this setting is enabled, diagnostic information about job and query execution is sent to Workload Manager. For more information, refer to Enabling workload analytics and logs collection.
    Enable Cluster Logs Collection When this option is enabled. the logs generated during deployments will be automatically sent to Cloudera. For more information, refer to Enabling workload analytics and logs collection.
  9. Click on Register Environment to trigger environment registration.
  10. The environment creation takes about 60 minutes. The creation of the FreeIPA server and Data Lake cluster is triggered. You can monitor the progress from the web UI. Once the environment creation has been completed, its status will change to “Running”.

After you finish

After your environment is running, perform the following steps: