Determine requirements for AWS instance about cor HOT 4 CLOSED

mmisw install has:

• 2 processors @ 2 cores (Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz)
• 16GB memory
• 250GB disk, 214GB of which is available

from cor.

Based on the enclose data for spot (on-demand) and provisioned instances, it seems the best strategy in the short term is going with a small (t2.medium) on-demand instance while we are setting up, then consider whether that seems to be working well or whether we should go for a hgher-powered system.

Although t2.medium has 2 CPUs (compared to 4 in production system), and 4 GB memory (compared to 16), at least during the setup process the impact should be minor.

I'm assuming straight Linux is fine. Will add a LAMP stack if that seems the way to go.

Data for spot instance

Data for reserved instance

from cor.

Based on the thread here, it appears the Amazon Linux is trying hard to be RedHat-like. I think we'll give it a try and see if it works well for this application.

Note: While CentOS was the target for the TAMU installation, and there is a CentOS distribution free for AWS, the fact the Amazon Linux is derived from CentOS suggests the similarity will be high. And we still get the value-add that Amazon has built into its Linux distribution.

from cor.

So the final answer is t2.medium with Amazon Linux. And off we go.

UPDATE: And, it seems worth buying a year's provisioned instance up front. It's much cheaper; even if we only use 6 months is the same cost; and it locks in the price. And it's the only way to get the t2.medium. There is an extra cost for the EBS storage but I think that should not be too expensive for a good while.

from cor.