The first step is to create and configure your AWS instance. This is where we'll store the Interana software and your data, and we have some specific recommendations for setting this up.
During this section of the Sandbox Deployment Guide, you will:
- Create an AWS account
- Create a security key to link to your Interana instance
- Create your own AWS instance, which is where you'll run Interana and store your data
- Configure settings for the AWS instance to make sure it can run Interana
- Start the AWS instance
First, go to https://aws.amazon.com/ and click Create an AWS account, or log into your account if you already have one.
You'll need more processing power and space to run Interana than is available from a free AWS account. Based on Amazon's calculator, it will cost approximately $300 per month to run your Interana instance (based on pricing for Amazon US-East).
After signing up you'll see the Welcome page for AWS. Click Launch Management Console to start.
You’ll start on the Amazon Web Services screen. Select Services > EC2 from the top menu.
The first thing you need to do is create a security key. Select Key Pairs in the left-hand menu, then click the Create Key Pair button on the page that appears.
Enter a name for the key; you can use any name, just make sure it's easy to find if you have a lot of keys! Then click Create. The key will be downloaded automatically; you’ll need to attach this key file in the last step of the AWS setup process.
Create an AWS instance
After creating the key, select Instances in the left-hand menu. Then click Launch Instance.
AWS will prompt you to choose an Amazon Machine Image (AMI). Find Ubuntu Server 14.04 LTS (HVM), SSD Volume Type AMI in the list, then click Select.
In the next screen, Choose an Instance Type, select the r3.xlarge type. Then click Next: Configure Instance Details to continue.
Even though it looks like the obvious choice, do not click Review and Launch! You'll click this only when you've completed the configuration process. For the rest of these steps, click the Next button to continue to the next step.
The next screen, Configure Instance Details, looks very complex. The good news is that you're not going to change anything. Click Next: Add Storage to continue.
Now you’ll see the Add Storage screen. Here you need to change the size of the Root volume. We recommend increasing this to 200GB to give your node enough space (the default value is too low, typically 8 or 50GB).
You can’t change the storage setting of your Root volume after launching your AWS instance. You can only add additional volumes. See the AWS documentation for mounting new volumes.
Once you've changed the Size, click Next: Add Tags.
Now you're on the Add Tags screen. Tags are optional, but can be useful for internal tracking. This isn't as important because you're creating a single-node instance, but feel free to add a tag like "Interana test instance." Then click Next: Configure Security Group to go to the next step.
In the Configure Security Group screen, you need to add entries for HTTP, HTTPS, and SSH protocols. Basically, this controls which IPs can access your cluster.
Fortunately, AWS can figure out your IP address automatically. In the Source field, select My IP. Now click Add Rule twice: add an entry for HTTP and then HTTPS. Select My IP for each type.
Review your settings
Now you can click Review and Launch. As the button says, you can review the settings to make sure they’re correct, and you can make changes before launching the instance.
Once you’ve confirmed that everything is OK, click Launch.
Select the key pair you created and launch the AWS instance
Now Amazon will ask you to select a key pair. If your key isn't selected automatically (and it probably will be), select Choose an existing key pair in the first drop-down list, then select the key you created in the second list.
Check the I acknowledge... box, then click Launch Instances. AWS will confirm that your instances are launching.
Click View Instances to get more information about your instance. Scroll down and find the Public DNS (IPv4) and copy that address (it's going to look like
ec2-##-##-###-###.compute-1.amazonaws.com). You'll need it in the next sections to log in to your system.