https://docs.protegrity.com/protectors/10.0/docs/bdp/bdp_aws_dbr/bdp_aws_dbr_install_prot/Recent content in Installing the Protector onHugoenhttps://docs.protegrity.com/protectors/10.0/docs/bdp/bdp_aws_dbr/bdp_aws_dbr_install_prot/bdp_aws_dbr_create_udf/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/protectors/10.0/docs/bdp/bdp_aws_dbr/bdp_aws_dbr_install_prot/bdp_aws_dbr_create_udf/<p>The following combinations will work for a successful execution of the configurator script:</p> <ul> <li>Databricks Dedicated Compute + Application Protector REST approach</li> <li>Databricks Dedicated Compute + Cloud Protector approach</li> <li>Databricks Standard Compute + Application Protector REST approach</li> <li>Databricks Standard Compute + Cloud Protector approach</li> <li>Databricks SQL Warehouse + Cloud Protector approach</li> </ul> <p>The Databricks SQL Warehouse + Application Protector REST approach combination will not work. This is because Protegrity executes a few Python commands on the Databricks Compute to retrieve a listening IP for the Application Protector REST&rsquo;s Server. When the Databricks Compute is a SQL Warehouse, the Python commands fail to execute. This occurs because the SQL Warehouse supports only SQL commands.</p>