# Update an Hyperscale Instance

Endpoint: PATCH /hyperscale-instances/{hyperscaleInstanceId}
Version: 3.23.0
Security: ApiKeyAuth

## Security:

  - `ApiKeyAuth` (unknown)
    apiKey in header Authorization

## Path parameters:

  - `hyperscaleInstanceId` (string, required)
    The ID of hyperscale instance.

## Request body:

  - `application/json` (unknown)
    Update parameters for a hyperscale instance.

## Request fields (application/json):

  - `name` (string)
    Name in DCT of the Hyperscale instance.

  - `hostname` (string)
    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` (string)
    API key to connect to the Hyperscale instance.

  - `data_type` (string)
    The data type designation for the hyperscale deployment.
    Enum: "ORACLE", "MSSQL", "DELIMITED_FILES", "MONGO_DB"

  - `insecure_ssl` (boolean)
    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.

  - `unsafe_ssl_hostname_check` (boolean)
    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.

## Response 200:

  - `200` (unknown)
    OK

## Response 200 fields (application/json):

  - `id` (string)
    The Hyperscale instance entity ID.

  - `name` (string, required)
    The name of this hyperscale instance.

  - `hostname` (string, required)
    The hostname of this hyperscale instance.

  - `data_type` (string)
    The data type designation for the hyperscale deployment.
    Enum: "ORACLE", "MSSQL", "DELIMITED_FILES", "MONGO_DB"

  - `creation_date` (string)
    The date this hyperscale instance was registered.

  - `tags` (array)
    The tags to be created for this hyperscale instance.

  - `tags.key` (string, required)
    Key of the tag
    Example: key-1

  - `tags.value` (string, required)
    Value of the tag
    Example: value-1

  - `api_key` (string, required)
    API key to connect to the hyperscale instance.

  - `insecure_ssl` (boolean)
    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.

  - `unsafe_ssl_hostname_check` (boolean)
    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.

  - `status` (string)
    The status of this hyperscale instance.
    Enum: "CREATED", "DELETING"

  - `connection_status` (string)
    The status of the connection to the hyperscale instance.
    Enum: "ONLINE", "CONNECTION_ERROR", "BAD_CREDENTIALS"

  - `connection_status_details` (string)
    If set, details about the status of the connection to the hyperscale instance.