Activating environments

This topic describes how to activate an environment to use for on (ECS).

Before you can create a Database Catalog to use with a Virtual Warehouse, you must activate a environment. Activating an environment causes to connect to the Kubernetes cluster, which provides the computing resources for the Database Catalog. In addition, activating an environment enables the service to use the existing data lake that was set up for the environment, including all data, metadata, and security.

Determine which environment that uses a particular data lake is the environment you want to activate for use with a Database Catalog and Virtual Warehouse.
In ECS environments, the Storage Class Name is automatically obtained from .
(Optional) Go to Advanced Configuration > Advanced Settings and enable the Use deterministic namespace names option to use deterministic namespaces for Kerberos principals and keytabs. You cannot enable this option after activating an environment.
(Optional) Go to Advanced Configuration > Advanced Settings and enable the Create databases for Virtual Warehouses option if you are upgrading the platform from an older release to the latest release, and you want to continue using external database for Hue and HMS. You cannot enable this option after activating an environment.
(Optional) Go to Advanced Configuration > Advanced Settings and turn off cluster validation by selecting the Skip cluster validation during environment activation option. By selecting this option, you can proceed with the environment activation even after seeing false positive errors in the logs. Cluster validation includes port validation, and the Kerberos keytab configuration validation, and Root CA certificate validation for Impala Virtual Warehouses.

Log in to service as DWAdmin.
Click on the Environments tab.
Locate the environment you want to activate and click Activate.
The Activate Environment dialog box is displayed.
Optional: Enable low resource mode to deploy on minimum hardware.

note
recommends that you use the Low Resource Mode option for proof of concept (POC) purposes only. This feature is not recommended for production deployment.
Complex queries and multiple queries on HS2 may fail due to limited memory configurations for HMS and HS2 in the low resource mode.
(To use mTLS) Browse and upload the database client certificate and database client private key files in PEM format.
The client certificate and private key files must be in PEM format.
Optional: Enable the Use dedicated nodes for executors option to schedule Hive and Impala executor and coordinator pods on the worker nodes tainted for .
Select the quota-managed resource pool from the Resource Pool drop-down menu.
The Resource Pool drop-down menu is displayed only if you have enabled the quota management feature from Advanced Configurations.
Click Activate.