The parameters to register a Hyperscale instance.
Hostname of the Hyperscale instance. If the Hyperscale instance is running on a custom port (not 443), the port can be specified using the "hostname:port" format, for instance "hyperscale-1.mycompany.co:1765"
API key to connect to the Hyperscale instance.
The data type designation for the hyperscale deployment.
Allow connections to the hyperscale instance over HTTPs without validating the TLS certificate. Even though the connection to the hyperscale instance might be performed over HTTPs, setting this property eliminates the protection against a man-in-the-middle attach for connections to this engine. Instead, consider configuring DCT with Certificate Authority certificates.
Ignore validation of the name associated to the TLS certificate when connecting to the hyperscale instance over HTTPs. Setting this value must only be done if the TLS certificate of the hyperscale instance does not match the hostname, and the TLS configuration of the hyperscale instance cannot be fixed. Setting this property reduces the protection against a man-in-the-middle attack for connections to this engine. This is ignored if insecure_ssl is set.
- Mock serverhttps://help-api.delphix.com/_mock/data-control-tower/continuous-compliance/2025.4.0.0/continuous-compliance-apis-dct-2025.4.0.0/hyperscale-instances
- https://help-api.delphix.com/dct/v3https://help-api.delphix.com/dct/v3/hyperscale-instances
curl -i -X POST \
https://help-api.delphix.com/_mock/data-control-tower/continuous-compliance/2025.4.0.0/continuous-compliance-apis-dct-2025.4.0.0/hyperscale-instances \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'Content-Type: application/json' \
-d '{
"name": "string",
"hostname": "string",
"api_key": "string",
"data_type": "ORACLE",
"insecure_ssl": false,
"unsafe_ssl_hostname_check": false,
"tags": [
{
"key": "key-1",
"value": "value-1"
}
],
"make_current_account_owner": true
}'Created
The data type designation for the hyperscale deployment.
Allow connections to the hyperscale instance over HTTPs without validating the TLS certificate. Even though the connection to the hyperscale instance might be performed over HTTPs, setting this property eliminates the protection against a man-in-the-middle attach for connections to this engine. Instead, consider configuring DCT with Certificate Authority certificates.
Ignore validation of the name associated to the TLS certificate when connecting to the hyperscale instance over HTTPs. Setting this value must only be done if the TLS certificate of the hyperscale instance does not match the hostname, and the TLS configuration of the hyperscale instance cannot be fixed. Setting this property reduces the protection against a man-in-the-middle attack for connections to this hyperscale instance. This is ignored if insecure_ssl is set.
The status of the connection to the hyperscale instance.
{ "id": "string", "name": "string", "hostname": "string", "data_type": "ORACLE", "creation_date": "2019-08-24T14:15:22Z", "tags": [ { … } ], "api_key": "string", "insecure_ssl": false, "unsafe_ssl_hostname_check": false, "status": "CREATED", "connection_status": "ONLINE", "connection_status_details": "string" }