通知を受け取る

UiPath Automation Suite

UiPath Automation Suite ガイド

手順 2: Automation Suite を Azure にデプロイする

このページでは、Automation Suite を Azure にデプロイするときに使用する必要があるパラメーターの概要を示します。

Once you have the Azure environment set up, navigate to this link to install Automation Suite in your Azure environment.

以下の表に、デプロイで使用するパラメーターの概要を示します。

Parameter nameDescription
SubscriptionThe Azure subscription.
Resource GroupThe Azure Resource Group, under the subscription.
RegionThe default region of the Resource Group.
LocationA valid Azure Region where the infrastructure is deployed. Make sure that the region has enough cores for the instance types used.
You can use the [resourceGroup().location] if this is the same as the Resource Group’s region.
Automation Suite versionThe version of Automation Suite.
Example: 21.10.2
Run Automation Suite InstallChoose whether Automation Suite should be installed after the infrastructure is provisioned.
Accept License AgreementBy setting the parameter as true, you agree to the applicable license agreement.
DNS Load BalancerThe prefix used for the load balancer subdomain.

If you use a custom domain you will only be able to access the cluster through the custom domain, not directly using the load balancer's domain (eg. ..cloudapp.azure.com).
Virtual Network New Or ExistingParameter indicating whether the Virtual Network used for the deployment should be created or if it already exists.
Existing Virtual Network Resource GroupResource group where the existing Virtual Network you want to use is deployed.

Parameter used only if the Virtual Network New Or Existing parameter is set to existing.
Existing Virtual Network NameName of the existing Virtual Network used for deployment.

Parameter used only if the Virtual Network New Or Existing parameter is set to existing.
Existing Subnet NameName of an existing subnet inside the previously mentioned Virtual Network. The subnet must satisfy these requirements.

Parameter used only if the Virtual Network New Or Existing parameter is set to existing.
Deploy Bastion HostDeploy a Bastion Host on the Virtual Network. Parameter used only if Virtual Network New Or Existing is set to new.
Enable Custom DomainSet to true if you want to use your own custom domain. The needs post-install configuration.
Custom domainThis is the domain you want to use for the cluster. Post-installation, create two CNAME/A records that will point to the public load balancer. See DNS configuration.
Enable Custom CertificatesSet to true if you want to use your own custom certificates for your own domain. Make sure to use this together with the Enable Custom Domain parameter set to true.
Custom Server CertificateThis is a base64 encoded string.

Encode the contents of the .crt server certificate to a base64 string. The server certificate should have the following properties.
Custom Server Cert KeyThis is a base64 encoded string.

Encode the contents of the .key server certificate key, to a base64 string. This is the private key from the Custom Server Certificate parameter.
Custom Server Cert Authority BundleThis is a base64 encoded string.

Create a .crt file containing all public certificates (.crt) from all of the CA certificates in the Server Certificate chain (excluding the server certificate).

Create a base64 string from the contents of this file.
Automation Suite Installer URLOptional: The link to the Automation Suite installation package.

Changing this parameter will overwrite the Automation Suite version parameter above and install the version specified in this URL.

Keep set to None if not used.
Automation Suite Advanced ConfigThis is a valid json string that will be merged in the cluster_config.json file that is being built by the template. Will overwrite existing settings.

See advanced installation experience for details.
Server Node CountThe number of VMs created to work as the servers for the cluster. Should be an odd number.
Server Node Instance TypeThe instance type for the server nodes.
Example: Standard_D16s_v3
Server Node HostnameServer node hostname/computer name prefix. For details on the appended sequence, see Azure documentation.
Enable Ultra DisksEnable to use ultra disks for etcd (server nodes). Should only be disabled if the region you are deploying to does not have zones support.
Agent Node CountThe number of VMs created to serve as the agent nodes for the cluster. If 0, an empty agent scale set is still created.
Agent Node Instance TypeThe instance type for the agent nodes.
Example: Standard_D16s_v3
Agent Node HostnameAgent node hostname/computer name prefix. For details on the appended sequence, see Azure documentation.
Gpu Node CountThe number of VMs with GPU created to be the agents for the cluster. Designed for ML workloads. If 0, no GPU scale set is created.
Gpu Node Instance TypeThe type of instances with GPU to be provisioned and to be the agents for the cluster.
Example: Standard_NC12s_v2
Gpu Node HostnameGPU node hostname/computer name prefix. For details on the appended sequence, see Azure documentation.
Task Mining Node TypeOptional: Instance type of the task mining node. This will only be used if you enable the Task Mining service. Example: Standard_B20ms
Task Mining Node HostnameTask Mining node hostname/computer name.
AS Robots Node CountThe number of dedicated Automation Suite Robots nodes. If 0, the scale set is still created.
AS Robots Node Instance TypeThe instance type for the dedicated Automation Suite Robots nodes.
Example: Standard_D16s_v3
AS Robots Node HostnameAutomation Suite Robots node hostname/computer name prefix. For details on the appended sequence, see Azure documentation.
SQL new or existingParameter indicating whether the SQL Server used for the deployment should be created or it already exists. For SQL server requirements, see our documentation .
SQL Server FQDN or IPFQDN or IP associated with the SQL Server. This is only used if the SQLNewOrExisting parameter is set to existing.
SQL Server UsernameSQL Server user login. If the SQL new or existing parameter is set to existing, this is the user for the existing SQL server. Otherwise, this username will be set on the SQL server created. For details on the required permissions, see our documentation for permissions.
SQL Server PasswordSQL Server user password. If the SQL new or existing parameter is set to existing, this is the user password for the existing SQL server. Otherwise, this password is set on the created SQL server.
SQL Server PortSQL Server port. If the SQLNewOrExisting parameter is set to existing, this port is used.
WarehouseSQLServerFqdnOrIPFQDN or IP associated with the Warehouse SQL Server. This is only used if the SQLNewOrExisting parameter is set to existing, and you want to install Process Mining.
WarehouseSQLServerUsernameWarehouse SQL Server user login. This is only used if you want to install Process Mining. If the SQLNewOrExisting parameter is set to existing, this is the user for the existing SQL server. Otherwise this username is set on the created SQL Server. For details on permissions, see Configuring Microsoft SQL server.
WarehouseSQLServerPasswordWarehouse SQL Server user password. This is only used if you want to install Process Mining. If the SQLNewOrExisting parameter is set to existing, this is the user password for the existing SQL server. Otherwise this password is set on the created SQL server.
WarehouseSQLServerPortWarehouse SQL Server port. This is only used if you want to install Process Mining. If the SQLNewOrExisting parameter is set to existing, this port is used.
UiPath Admin UsernameThe admin username to be set on all nodes. This is also used as the host tenant admin.
UiPath Admin PasswordThe password for the node admin user. This is also used as the host tenant admin password.
Vm Admin UsernameThe admin username to be used in the virtual machine instances.
Vm Admin PasswordThe admin password to be used in the virtual machine instances.
Enable Cluster BackupSet to true if you want to deploy the external NFS file share. Also, the backup will be enabled at cluster level if the Run Automation Suite Install parameter is set to true.
Services Install flags (multiple)Choose if the specific service is installed in the cluster.
AI Center Connect To External Orchestrator FlagFlag which determines whether AI Center connects to an external Orchestrator. Only works if AiCenterInstallFlag is set to 'true'. You need to specify how AI Center connects to the Orchestrator in the following parameters.
OrchestratorUrlThe URL for Orchestrator to which AI Center connects. Fill this in only if you want to install AI Center and connect it to an external Orchestrator and Identity Service.
IdentityUrlThe URL for the Identity Service to which AI Center connects. Fill this in only if you want to install AI Center and connect it to an external Orchestrator and Identity Service.
OrchestratorCertficateThe Certificate in Base64 for the Orchestrator to which AI Center connects. Fill this in only if you want to install AI Center and connect it to an external Orchestrator and Identity Service.
IdentityCertificateThe Certificate in Base64 for the Identity Service to which AI Center connects. Fill this in only if you want to install AI Center and connect it to an external Orchestrator and Identity Service.
Tags by resourceOptional: Tags per resource. Can be empty or have the following format:
{ "Microsoft.Web/serverFarms": { "<TagName>": "<TagValue>" }, "Microsoft.Insights/components": { "<TagName>": "<TagValue>" } }

20 日前に更新


手順 2: Automation Suite を Azure にデプロイする


このページでは、Automation Suite を Azure にデプロイするときに使用する必要があるパラメーターの概要を示します。

改善の提案は、API リファレンスのページでは制限されています

改善を提案できるのは Markdown の本文コンテンツのみであり、API 仕様に行うことはできません。