Deploying Connector in AWS

If you are not installing the Ivanti Neurons for MDM Connector on AWS, skip ahead to Connector Requirements.

Deploying the EC2 instance

To deploy the EC2 instance:

  1. Log in to AWS with administrator credentials.

  2. On the AWS services page, select EC2 under Compute.

  3. Expand Images and select AMIs in the left pane.

  4. Select Public Images from the drop-down list in the right pane.

  5. Search for the Ivanti Neurons for MDM Connector using keywords such as "MobileIron," "Cloud Connector."

  6. Select the latest version of the connector from the list.

  7. From the console dashboard, choose Launch Instance.

  8. On the Choose an Instance Type page, select the t2.medium or t3.medium type. t3 type supported with Connector version 81 and later.

  9. Choose Review and Launch to let the wizard complete the other configuration settings for you.

  10. On the Review Instance Launch page, under Security Groups, you'll see that the wizard created and selected a security group for you. You can use this security group, or alternatively you can select the security group that you created when getting set up using the following steps:

  11. Choose Edit security groups.

  12. On the Configure Security Group page, ensure that Select an existing security group is selected.

  13. Select your security group from the list of existing security groups, and then choose Review and Launch.

    1. On the Review Instance Launch page, under Tags:

    2. Choose Edit Tags.

    3. Choose Add Tag.

    4. In the Key field, type Name.

    5. In the Value filed, type Mobileiron-connnector.

  14. Choose Review and Launch.

  15. On the Review Instance Launch page, choose Launch.

  16. When prompted for a key pair, select Choose an existing key pair, then select the key pair that you created earlier.

  17. Alternatively, you can create a new key pair. Select Create a new key pair, enter a name for the key pair, and then choose Download Key Pair.

  18. This is the only chance for you to save the private key file, so be sure to download it. Save the private key file in a safe place. You'll need to provide the name of your key pair when you launch an instance and the corresponding private key each time you connect to the instance.

    Do not select the Proceed without a key pair option. If you launch your instance without a key pair, then you can't connect to it.

  19. When you are ready, select the acknowledgement check box, and then choose Launch Instances. A confirmation page lets you know that your instance is launching.

  20. Choose View Instances to close the confirmation page and return to the console.

  21. On the Instances screen, you can view the status of the launch. It takes a short time for an instance to launch. When you launch an instance, its initial state is pending. After the instance starts, its state changes to running and it receives a public DNS name. (If the Public DNS (IPv4) column is hidden, choose Show/Hide Columns (the gear-shaped icon) in the top right corner of the page and then select Public DNS (IPv4).)

  22. It can take a few minutes for the instance to be ready so that you can connect to it. View the Status Checks column to see if your instance has passed its status checks.

  23. SSH to the newly-created instance using the user name: operations.

    Setup starts and displays the End User License Agreement (EULA).

  24. Accept the EULA and proceed.

    A privileged access password is required for protected access to privileged commands.

  25. Enter a privileged access password.

  26. Confirm the password.

  27. Enter the Administrator user name: miadmin

  28. Enter an administrator password.

  29. Confirm the password.

  30. Skip the IP address settings so that DHCP is used.

    Do not skip to provide DNS servers info.

  31. On following screen, enter the DNS servers information, making sure not to use the default settings.

For more information about the configuration wizard, see: Using the Configuration Wizard.