Deploy a fleet blueprint

This name will be added to all deployed instances, instance templates and virtual networks
Optional. The resource group in which all resources will be created. Defaults to Fleet Manager's resource group.
License
You have not yet entered a Dataiku license or license token. A license or license token is needed to deploy instances. You can leave blank and enter this later (in "Cloud Setup").
Tags
 These tags will be added to all cloud resources created as part of this fleet.
Network
Use Fleet Manager's virtual network or select a custom one.
Virtual Network in which the fleet will be deployed
Optional. If not specified, the machine will be deployed in the same region as FM without specific availability zone
DNS
Load balancer
The load balancer will be created with the minimal settings requirement.
It is mandatory to have a second subnet for the load balancer.
It is mandatory to have a second subnet for the load balancer.
Used by the load balancer to map the user request to a node.
Used by the load balancer to map the user request to a node.
Used by the load balancer to map the user request to a node.
Used by the load balancer to map the user request to a node.
Instance settings
Used to grant SSH access to the DSS instances (recommended).
In order for the deployed instances to be able to manage clusters, the instances must be associated to an IAM role that has required permissions on EKS and ECR. Enter here the instance profile ARN of this role.
Azure requires a ssh key to be able to login onto the instances.
In order for the deployed instances to be able to manage clusters, the instances must be associated to a managed identity that has required permissions on AKS and ACR. Enter here the managed identity of this role.
A ssh key to be able to login onto the instances (recommended, if not using project-wide ssh keys)
In order for the deployed instances to be able to manage clusters, the instances must be associated to a service account that has required permissions on GKE and GAR. Enter here the service account of this role.
If different from project of this Fleet Manager instance
Disks
Optional, cannot be renamed later
Optional, cannot be renamed later
Optional, cannot be renamed later
Optional, cannot be renamed later
Optional, cannot be renamed later
Optional, cannot be renamed later
Optional, cannot be renamed later
Optional, cannot be renamed later
  • A single DSS design node will be deployed on a new EC2 machine in the current VPC and subnet
  • A single DSS design node will be deployed on a new machine in the current VNet and subnet
  • The deployed design node will not have elastic computation capabilities ready to use
  • DSS will be accessible on HTTPS using self-signed certificates
  • After creating this fleet, you will be able to review and modify all settings, including security settings, HTTPS settings, ...
  • You will then need to actually provision instances in order for them to become available
  • A single DSS design node will be deployed on a new EC2 machine in the current VPC and subnet
  • A single DSS design node will be deployed on a new machine in the current VNet and subnet
  • The deployed design node will have elastic computation capabilities ready to use. You will need to go in the "Clusters" section of the DSS administration in order to create your first computation cluster
  • DSS will be accessible on HTTPS using self-signed certificates
  • After creating this fleet, you will be able to review and modify all settings, including security settings, HTTPS settings, ...
  • You will then need to actually provision instances in order for them to become available
  • A single DSS design node will be deployed on a new EC2 machine in the current VPC and subnet
  • A single DSS design node will be deployed on a new machine in the current VNet and subnet
  • The deployed nodes will have elastic computation capabilities ready to use. You will need to go in the "Clusters" section of the DSS administration in order to create your first computation cluster
  • The deployer will be preconfigured to deploy projects to the automation node, and to deploy APIs to the Elastic clusters
  • DSS will be accessible on HTTPS using self-signed certificates
  • After creating this fleet, you will be able to review and modify all settings, including security settings, HTTPS settings, ...
  • You will then need to actually provision instances in order for them to become available
  • A single DSS design node will be deployed on a new EC2 machine in the current VPC and subnet
  • A single DSS design node will be deployed on a new machine in the current VNet and subnet
  • The deployed nodes will have elastic computation capabilities ready to use. You will need to go in the "Clusters" section of the DSS administration in order to create your first computation cluster
  • The deployer will be preconfigured to deploy projects to the automation node, and to deploy APIs to the Elastic clusters
  • In addition, an additional "centralized admin" DSS design node will be deployed
  • All nodes will centralize their audit logs to the centralized admin node
  • DSS will be accessible on HTTPS using self-signed certificates
  • After creating this fleet, you will be able to review and modify all settings, including security settings, HTTPS settings, ...
  • You will then need to actually provision instances in order for them to become available
  • You will need to configure the centralized admin node's event server to indicate where to write the centralized audit logs