"If you are planning to do this (I certainly am), don't forget that the T2 instances do not include any local (instance) storage and that you'll need to use one or more EBS volumes instead."
I find that bit a bit of a shame as we deploy using local instance storage only and avoid EBS.
The approach I am taking to EC2 instances is that I can kill it any time. So fire up instance, fetch latest code zip from S3 (not from Github), and deploy that code. Runs smoothly.
Keeps it very simple and effective, I can even ramp up the number of instances then reduce them to retire old instances.
EBS adds another point of failure (and probably the weakest link in the Amazon stack) and overcomplicates deployment.
EBS has historically had a few issues, and the performance is fairly poor. I've personally never had any issues with them in the 4 years that I've used AWS.
Comments
"If you are planning to do this (I certainly am), don't forget that the T2 instances do not include any local (instance) storage and that you'll need to use one or more EBS volumes instead."
I find that bit a bit of a shame as we deploy using local instance storage only and avoid EBS.
Why do you avoid EBS? Cost?
The approach I am taking to EC2 instances is that I can kill it any time. So fire up instance, fetch latest code zip from S3 (not from Github), and deploy that code. Runs smoothly.
Keeps it very simple and effective, I can even ramp up the number of instances then reduce them to retire old instances.
EBS adds another point of failure (and probably the weakest link in the Amazon stack) and overcomplicates deployment.
EBS has historically had a few issues, and the performance is fairly poor. I've personally never had any issues with them in the 4 years that I've used AWS.