Cloud Settings

[Azure only] Your Azure subscription name.

The region (defined by your cloud provider) where the VMs will run. In this region, the pool and additional Helper VMs will be created. It is recommended to select the same region for the Initiating VMs and the pool and Helper VMs, in order to avoid network latency. 

Select Private to use a Virtual Private Network on the cloud for launching and running Helper VMs, thus adding another layer of security for your transferred data. To use this option, you must already have a private network on your cloud provider. This option can sometimes reduce data transfer speeds.

Your Coordinator host should be connected to the private network as follows:

• If your Coordinator is not on the cloud, the Coordinator host must be connected to the cloud private network via VPN.

• If your Coordinator is on the cloud, its host must have access to the selected subnet. 

Proxy: For Linux users, you can configure your Cloud Helpers to communicate with Incredibuild Cloud via a proxy server. This also requires setting the following environment variables on your Incredibuild Coordinator machine: http_proxy, https_proxy.

Incredibuild creates cloud network resources to contain your cloud VMs. This option is only available when you specify a Public network.

[Azure only] All the resources that are created by Incredibuild Cloud for build acceleration, belong to one resource group. You can change the default name of this resource group before activating the solution.

If you do not add a customized name for the resource group, Incredibuild Cloud will use a default value, which includes your Coordinator ID.

You can also manage VMs and Network in different resource groups, limiting Incredibuild Cloud Agents from accessing to the Resource Group used for your network

The VPC that will contain your public or private cloud network. Called Virtual Network for azure and VPC for AWS.

These settings are only visible when installing directly from AWS marketplace. They are the ports required to communicate with your Coordinator.

Incredibuild's permissions and activities in your cloud account are limited to a Security Group. If you do not select this option, we create a Security Group for you and open the required ports. If you select this option, you can use your own Security Group, however you will need to manually open some ports to facilitate communication with items in the Security Group. For details, see Using your Own Security Group below.

Note: In GCP, this setting is called a Firewall Rule, and no selection is required (just toggle on or off).

Coordinator

This setting is only visible when installing directly from AWS marketplace. It is the type of the VM that will serve as your Coordinator. We recommend leaving the default setting. If you need to change this machine after creating your environment, see Changing your Coordinator Machine.

Helpers

This allows you to create Cloud Helpers on Linux machines. For details, see Smart Compatibility Layer.

Enable Spot instances to get access to unused cloud compute at deep discounts. For details, see Enable Spot Instances.

The type of the VMs that will serve as Helper Agents. We recommend using machines with at least 8 or 16 cores. If you are using Unreal Engine, your VMs should have at least 100GB HDD with 70 GB dedicated for cache.

The disk type that will contain your virtual machines.

The storage size on each virtual machine.

The number of seconds that need to pass after a VM has finished executing a task, before it is automatically deactivated. When deactivated, the VM will return to the pool if it is not full, otherwise it will be terminated. The default is 90 seconds. Values can be 60-43200.

If your organization requires it, you can specify a custom VM role that will be attached to your cloud VMs. You also need to modify the JSON that provides Incredibuild with permissions to your AWS account.

You can specify more than one role in the JSON for convenience, however you can only specify one role at a time that will attached to the VMs in this user interface.

Pool Settings

The maximum number of cores that can be used to run your builds.

Incredibuild maintains a pool of machines in a Sleep state to speed up the process of ramping up machines when they are needed.

The number of VMs that will be created for Incredibuild Cloud pool, and will be moved automatically into a Sleep state. After their creation, these VMs are not automatically used by the Coordinator, but they can start to work immediately as Helpers upon the Coordinator request.

The value cannot be higher than Max Number of Cores multiplied by the number of cores in your Default Machine Type.

Fallback Machine Types

This section is only for AWS and Azure. In GCP, fallbacks are managed on their side automatically.

If you are using Spot machines, you can also enable Incredibuild to use On-Demand (non-spot) machines if no Spot machines are available using this checkbox.

If your cloud provider runs out of the Default Machine Type, Incredibuild will use other machine types. We only try to find machines that are in the same family type as your Default Machine Type. Generally the prices of these machines are similiar to the price of your Default Machine type, however we cannot control the prices in your cloud provider.

If your cloud provider runs out of the Default Machine Type, Incredibuild will use other machine types. You can limit the types of machines by specifying the machine types to use here.

[Optional] Custom tags that will be added automatically to the following resources, which that are created by Incredibuild on your cloud provider:

• AWS: Virtual Machines, VPCs, Subnets, Roles

• Azure: Virtual Machines, Disk Drives. Network Interfaces, Public IP Addresses

Notes: 

• You can add up to 5 custom tags, by defining for each tag a name:value pair.

• For more information on resource tagging in AWS, see the AWS documentation.

• In AWS, you can use cost allocation tags to find your machine cost.

• All Azure cloud resources that are created by Incredibuild include "cloud" in their name.

When using Incredibuild 10, you can enable SSL for communication between your Incredibuild components.

Upload an SSL certificate and key to place on your cloud agents. You will need to enable SSL on your Coordinator as well.

This is not supported for AWS marketplace.

When using Linux, you can collect the logs from Cloud Helpers and other volatile machines in a single remote location to help you troubleshoot or understand your builds. For details, see Collecting Build Logs in the Linux Documentation.

This email will be used by Incredibuild for confirmations, notifications, and assistance. This email will not be used for promotions or marketing.

Used by the VMs that are running as Helpers on the cloud to communicate with the Coordinator. This must be the same as the Coordinator Service port in the Coordinator Settings.

The default is 31105.

Verify that this port is open for external traffic in your organization firewall.