Deploying MobileIron Connector in AWS
If you are not installing the MobileIron Cloud 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 Cloud 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 type. |
|
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: |
|
a.
|
Choose Edit security groups. |
|
b.
|
On the Configure Security Group page, ensure that Select an existing security group is selected. |
|
c.
|
Select your security group from the list of existing security groups, and then choose Review and Launch. |
|
11.
|
On the Review Instance Launch page, under Tags: |
|
c.
|
In the Key field, type Name. |
|
d.
|
In the Value filed, type Mobileiron-connnector. |
|
e.
|
Choose Review and Launch. |
|
12.
|
On the Review Instance Launch page, choose Launch. |
|
13.
|
When prompted for a key pair, select Choose an existing key pair, then select the key pair that you created earlier. |
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.
|
14.
|
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. |
Note: Don't select the Proceed without a key pair option. If you launch your instance without a key pair, then you can't connect to it.
|
15.
|
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. |
|
16.
|
Choose View Instances to close the confirmation page and return to the console. |
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).)
|
17.
|
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. |
|
18.
|
SSH to the newly-created instance using the user name: operations. |
Setup starts and displays the End User License Agreement (EULA).
|
19.
|
Accept the EULA and proceed. |
A privileged access password is required for protected access to privileged commands.
|
20.
|
Enter a privileged access password. |
|
21.
|
Confirm the password. |
|
22.
|
Enter the Administrator user name: miadmin |
|
23.
|
Enter an administrator password. |
|
24.
|
Confirm the password. |
|
25.
|
Skip the IP address settings so that DHCP is used.
|
Note: Do not skip to provide DNS servers info.
|
26.
|
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.