Activating Azure environments
To use an Azure environment for Cloudera Data Warehouse (CDW) Public Cloud you must use these instructions to activate it.
Before you can create a Database Catalog to use in a Virtual Warehouse, you must activate an environment that has been registered in Management Console. How you activate the environment determines key capabilities of CDW, such as what data you can access.
A Database Catalog can use different Data Lake types, including the following ones:
- Shared Data Experience (SDX) Data Lake types
- Cloudera Data Warehouse (CDW) Data Lake types
The type of Data Lake used by the Database Catalog for your Virtual Warehouse determines whether or not you can access data in Data Hubs, and other clusters, from CDW.
If you start (activate) the environment from Environments, which you might be inclined to do immediately after registering the environment, the Database Catalog gives you access from CDW to an SDX Data Lake. If you navigate to Cloudera Data Warehouse and activate an environment from the CDW service, the Database Catalog gives you access from CDW to a CDW Data Lake.
Required role: DWAdmin
- Determine which environment (and related data lake) you want to activate for use with a Database Catalog and Virtual Warehouse.
- Review the requirements checklist for your environment.
- In the CDW service, expand the Environments column by clicking More….
- In Environments, search for and locate the environment that you want to activate.
Click the start icon
to activate the environment.
In the Activation Settings, configure the environment or accept
- Select the Compute VM Size based on your Impala workload.
E16_v3 uses Standard_E16_v3 Virtual Machine size and
E16ds_v4 uses Standard_E16ds_v4 Virtual Machine
E16ds_v4 is the default setting.
- Optionally, select Enable availability zones for AKS.
- Optionally, specify a user-assigned, managed identity for the AKS cluster.
- Select a Subnet inside the virtual network (VNet) that you
want to use for CDW.
The VNet that you select must have a sufficient number of free IP addresses.
- Select Enable internal load balancer (ingress) to distribute traffic inside a virtual network.
- Select Enable AKS monitoring and then select the workspace from the adjacent drop-down list.
- Select Enable private CDW to create a private cluster after meeting prerequisites.
- Add any trusted endpoint IP CIDRs as appropriate for your environment in a comma-separated list to the Whitelist IP CIDRs text box.
- Select Use kubenet networking if IP address exhaustion is a concern for your deployment.
- Select the Compute VM Size based on your Impala workload. E16_v3 uses Standard_E16_v3 Virtual Machine size and E16ds_v4 uses Standard_E16ds_v4 Virtual Machine size.
- Click Activate.