Manage DW Service Units
Relyt allows you to manage your DW service units, including:
Before you start
Ensure you have obtained either the main account or a subaccount with the SYSTEMADIN
system role.
Create a DW service unit
You can create as many DW service units you need. These DW service units can be deployed in different regions of different public clouds.
-
Sign in to your data cloud as a cloud account with the
SYSTEMADMIN
system role.If you sign in as the main account, switch your role to
SYSTEMADMIN
. -
On the upper-right corner of the page, click + Service Unit.
-
On the Create Service Unit, select the edition, cloud provider, and region, and then click Continue.
The following table describes the related parameters.
Parameter Required Description Edition Yes It is fixed to Standard. Cloud Provider Yes The cloud provider that provides the cloud computing resources to power the DW service unit. Region Yes The region in which the DW service unit resides.
-
Set the domain name and alias for the servcie unit, and click Continue.
The following table describes the related parameters.
Parameter Required Description Domain Name Yes The custom part in the complete domain name of the DW service unit. A complete domain name is in the <custom_part>
.data.cloud format. The custom part must be 4 to 32 characters in length, start with a letter, and contain only letters, digits, and hyphens (-).Alias No The alias of the DW service unit. It should be short and distinguishable.
-
Create the default Hybrid DPS cluster for the service unit.
The following table describes the related parameters.
Parameter Required Description Name Yes The name of the Hybrid DPS cluster. It must start with a letter, and can contain only letters, digits, and hyphens (-). It must be 4 to 32 characters in length. Size Yes The size of the Hybrid DPS cluster. Description No The description of the Hybrid DPS cluster. -
Click Finish.
Manage network policies for an existing service unit
If you want to implement granular access control on your service unit, you can create a network policy for your service unit to specify which IP addresses can access or which cannot and activate it to enforce the policy.
For detailed procedure, see "Create a network policy" and "Activate a network policy" in Network Policies.
View basic information about a service unit
After signing in, you can view a list of information cards that display the basics about each service unit. In addition, you can perform the following steps to view the connection information about a service unit:
-
Sign in your data cloud using a cloud account.
-
Find the information card of the target DW service unit, click the ... button, and choose Connection Information from the drop-down list.
On the page that is displayed, you can view the connection information about the service unit.
Transfer ownership
Ownership of a DW service unit, by default, is held by its creator. Relyt provides functionality for owners to transfer ownership to another account.
Once you transfer ownership of a DW service unit to another account, it can no longer be managed from your current account.
-
Sign in to Relyt using a cloud account with the
SYSTEMADMIN
system role.If you sign in as the main account, switch your role to
SYSTEMADMIN
. -
Find the information card of the target DW service unit, click the ... button, and choose Transfer Ownership from the drop-down list.
-
In the Transfer Ownership dialog box, select the cloud account to which you want to transfer ownership and click Transfer.
After the ownership has transferred, you can click the Ownership Transfer History button on the upper right corner of the DW Service Units page to verify the details, including the DW service unit name, transfer time, and new owner.
Manage private links
You can use private links between your DW service unit and a third-party virtual private cloud (VPC) to enhance data security.
For detailed operations, see Private Link.
Manage network policies
You can configure network policies to manage access to your DW service unit.
For detailed operations, see Network Policies.