What are the basic steps for deploying a virtual machine in Azure?

Define the Deployment

1. Configure the following properties:
   Define Deployment PropertyDescription

   Deployment Name	Name of the deployment. Use a brief name that informs your team of the deployment use case.
   Deployment Type	Select one of the following types: Self-managed Amazon EC2 Google Compute Engine [GCE] Azure Virtual Machine [Azure VM]
   Environment	Active environment where engine instances will be deployed. The selected deployment type determines the list of environments that display. For example, if creating an Azure VM deployment, then you can select an active Azure environment.
   Engine Type	Type of engine to deploy: Data Collector Transformer
   Engine Version	Engine version to deploy.
   Deployment Tags	Optional tags that identify similar deployments within Control Hub. Use deployment tags to easily search and filter deployments. Enter nested tags using the following format: //

2. Click one of the following buttons:
   • Cancel - Cancels creating the deployment and exits the wizard.
   • Save & Next - Saves the deployment and continues.
   • Save & Exit - Saves the deployment and exits the wizard, displaying the incomplete deployment in the Deployments view.

Configure the Engine

1. Configure the following properties:
   Engine PropertyDescription

   Stage Libraries	Stage libraries to install on the engine. The available stage libraries depend on the selected engine type and version.
   Advanced Configuration	Access to advanced configuration properties to further customize the engine. As you get started with StreamSets, the default values should work in most cases. The available properties depend on the selected engine type.
   External Resource Source	Source of the external files and libraries, such as JDBC drivers, required by the engine: None - External resources are not defined in the deployment. Select when using a single engine instance to get started with StreamSets, or when your pipelines do not require external resources. Archive File - External resources are included in an archive file defined in the deployment. Select when the deployment launches multiple engine instances and when your pipelines require external resources.
   External Resource Location	Location of the archive file that contains the external resources used by the engine. The archive file must be in TGZ or ZIP format. Store the file in an Azure Blob Storage or Azure Data Lake Storage Gen2 container and share the URL publicly. Then enter the location to the container using an HTTP URI. For example: //.blob.core.windows.net///externalResources.tgz Tip: Click the download icon to download a sample externalResources.tgz file to view the required directory structure. Available when using an archive file as the source for external resources.
   Engine Labels	Labels to assign to all engine instances launched for this deployment. Labels determine the group of engine instances that run a job. Default is the name of the deployment.

2. Click one of the following buttons:
   • Back - Returns to the previous step in the wizard.
   • Save & Next - Saves the deployment and continues.
   • Save & Exit - Saves the deployment and exits the wizard, displaying the incomplete deployment in the Deployments view.

Configure Azure VM Zones

1. Select the zones to provision the VM instances in.
2. Click one of the following buttons:
   • Back - Returns to the previous step in the wizard.
   • Save & Next - Saves the deployment and continues.
   • Save & Exit - Saves the deployment and exits the wizard, displaying the incomplete deployment in the Deployments view.

Configure the Azure VM Autoscaling Group

1. Configure the following properties:
   Azure VM Autoscaling Group PropertyDescription

   Engine Instances	Number of engine instances to deploy. For each engine instance, Azure Resource Manager provisions a VM instance in the VNet, and then deploys and launches one engine instance on each VM instance. Important: If your pipelines require external resources, you must set up an external resource archive that all engine instances can access before increasing the number of engine instances.
   VM Size	Size to use for the provisioned VM instances. For more information about VM sizes, see the Azure Virtual Machines documentation.
   Managed Identity	Managed identity to associate with the provisioned VM instances. Select the managed identity created as an environment prerequisite by your Azure administrator. If a default managed identity is defined for the Azure environment, you can accept the default or override it with a different managed identity.
   Resource Group	Resource group that the provisioned VM instances are assigned to. Select the resource group created as an environment prerequisite by your Azure administrator. If a default resource group is defined for the Azure environment, you can accept the default or override it with a different resource group.
   Azure Tags	Tags to apply to all Azure resources provisioned for this deployment. Enter the tags as key-value pairs. For tag naming requirements, see the Azure Resource Manager documentation. You can define the tags using simple or bulk edit mode. In simple edit mode, click Add Another to define additional tags. In bulk edit mode, configure tags in JSON format. Important: These tags are applied to Azure resources, not to Control Hub deployments.
   Init Script	Initialization script to run on each provisioned instance. Use the script to set up provisioned instances with additional software as required by your organization. The script must be a valid shell script with a maximum size of 8 KB. Enter the script directly in the property or upload a shell script file that uses an .sh extension. After uploading, you can edit the contents of the script. Important: You must include a specific init script when the Azure VNet uses custom DNS servers.

2. Click one of the following buttons:
   • Back - Returns to the previous step in the wizard.
   • Save & Next - Saves the deployment and continues.
   • Save & Exit - Saves the deployment and exits the wizard, displaying the incomplete deployment in the Deployments view.

Configure Azure VM SSH Access

1. Configure the following properties:
   Azure VM SSH Access PropertyDescription

   SSH Key Source	Source for the SSH keys: Public SSH Key - Assigns the full contents of a public SSH key to the provisioned VM instances. Existing SSH Key Pair Name - Assigns an existing SSH key pair in your Azure account to the provisioned VM instances.
   Public SSH Key	Full contents of the public SSH key to assign to the provisioned VM instances. Enter the contents of the key created as a deployment prerequisite.
   Key Pair Name	Name of the existing Azure key pair to assign to the provisioned VM instances. Select the key pair created as a deployment prerequisite by your Azure administrator.
   Attach Public IP	Attaches a public IP address to the provisioned VM instances. Select when you need to use SSH from a machine outside of the Azure VNet to access the VM instances.

2. Click one of the following buttons:
   • Back - Returns to the previous step in the wizard.
   • Save & Next - Saves the deployment and continues.
   • Save & Exit - Saves the deployment and exits the wizard, displaying the incomplete deployment in the Deployments view.

Share the Deployment

1. In the Select Users and Groups field, type a user email address or a group name.
2. Select users or groups from the list, and then click Add.

   The added users and groups display in the User / Group table.

3. Modify permissions as needed. By default, each added user or group is granted the following permissions:
   • Read - View the details of the deployment and of all engines managed by the deployment. Restart or shut down individual engines managed by the deployment in the Engines view.
   • Write - Edit, start, stop, and delete the deployment. Delete engines managed by the deployment. Also requires read access on the parent environment.
   • Execute - Start jobs on engines managed by the deployment. Starting jobs also requires execute access on the job and read access on the pipeline.

   For more information, see Deployment Permissions.

4. Click one of the following buttons:
   • Back - Returns to the previous step in the wizard.
   • Save & Next - Saves the deployment and continues.
   • Save & Exit - Saves the deployment and exits the wizard, displaying the incomplete deployment in the Deployments view.

Review and Launch the Deployment

1. Click one of the following buttons:
   • Exit - Saves the deployment and exits the wizard, displaying the Deactivated deployment in the Deployments view. You can start the deployment at a later time.
   • Launch Deployment - Starts the deployment, provisions VM instances in your Azure account, and launches a StreamSets engine on each instance.

     Note: It can take a few minutes to provision the VM instances and then launch the StreamSets engine instances.

2. If the deployment launches a Transformer engine that works with a Spark cluster, you must grant the Spark cluster access to Transformer.

Instances

In the overview page of the virtual machine scale set, click . The Azure portal lists all VM instances provisioned for the deployment.

Click an instance name to view specific details about the VM instance, including the public and private IP addresses. For example, the following image displays a sample VM instance details page:

Resource Group

In the overview page of the virtual machine scale set, click the name of the resource group. The Azure portal displays the overview page for the resource group.

To view all deployments created for the resource group, click . The Azure portal lists each deployment with a Succeeded or Failed status, as follows:

Click the name of the first deployment in the list to view the deployment overview page. Expand the deployment details to access the public IP addresses, as follows: