Supported Qubole Endpoints on Different Cloud Providers
Qubole provides QDS on AWS, Microsoft Azure, Google Cloud Platform, and Oracle Cloud infrastructure clouds through the endpoints shown below.
Note
In JDBC and ODBC driver configurations, https://api.qubole.com is the default endpoint. The suffix /api/${V}/ is not required in JDBC/ODBC driver configurations.
Supported Qubole Endpoints on QDS-on-AWS
Qubole provides QDS on the AWS cloud through different endpoints, which are entry points to access QDS. For more information, see Overview.
Qubole now supports only HTTPS. All HTTP requests are now redirected to HTTPS. This is aimed at better security for Qubole users.
The endpoints are described in the following table. APIs for QDS-on-AWS are supported on API v1.2, v1.3, and
v2 versions even though only some QDS components are supported only on v1.3 and v2 versions. The supported list
is mentioned in Overview.
API Endpoints/Access URLs |
QDS Environment/Description |
Security Certification |
|---|---|---|
|
https://api.qubole.com is the URL to access UI. It is the oldest and default environment to access QDS on the AWS cloud. |
NA |
|
https://eu-central-1.qubole.com is the correct URL. It is the environment for QDS on the AWS cloud. |
SOC2 and ISO 27001 compliant |
|
https://in.qubole.com is the correct URL. It is the environment for QDS on the AWS cloud. |
SOC2 and ISO 27001 compliant |
|
https://us.qubole.com is the correct URL. It is the environment for QDS on the AWS cloud. |
SOC2 and ISO 27001 compliant |
|
https://wellness.qubole.com/ is the correct URL. It is the environment for QDS on the AWS cloud. The use of https://wellness.qubole.com falls under the HIPAA compliance safeguards and requires a Business Associates Agreement (BAA) prior to use. For more information, contact the Account Executive or Qubole Support. |
HIPAA, SOC2, and ISO 27001 compliant |
Supported Qubole Endpoints on QDS-on-Azure
Qubole provides QDS on the Microsoft Azure cloud through the endpoint that is mentioned in this table. APIs for QDS-on-Azure
are supported on api/v2, so, ${V} = v2.
Endpoint |
QDS Environment/Description |
Security Certification |
|---|---|---|
|
https://azure.qubole.com/ is the correct URL. It is the environment to access QDS on the Microsoft Azure cloud. |
SOC2 and ISO 27001 compliant |
Supported Qubole Endpoints on QDS-on-GCP
Qubole provides QDS on the Google Cloud Platform (GCP) through the endpoint that is mentioned in this table. APIs for QDS-on-GCP
are supported on either api/v2 (Account API and Cluster API) or api/v1.2 (all other APIs), so, ${V} = v2 or v1.2 as appropriate.
Endpoint |
QDS Environment/Description |
Security Certification |
|---|---|---|
|
https://gcp.qubole.com/ is the correct URL. It is the environment to access QDS on the Google Cloud Platform (GCP). |
SOC2 and ISO 27001 compliant |
|
https://gcp.qubole.com/ is the correct URL. It is the environment to access QDS on the Google Cloud Platform (GCP). |
SOC2 and ISO 27001 compliant |
Supported Qubole Endpoints on QDS-on-OCI
Qubole provides QDS on the Oracle Cloud Infrastructure (OCI) cloud through the endpoint that is mentioned in this table.
APIs for QDS-on-Azure are supported on api/v2, so, ${V} = v2.
Endpoint |
QDS Environment/Description |
Security Certification |
|---|---|---|
|
https://oraclecloud.qubole.com/ is the correct URL. It is the environment to access QDS on the OCI cloud. |
SOC2 and ISO 27001 compliant |