To be honest SSH-ing into boxes is just a tiny bit before my time but here are some notes anyways.
Warning: This section is under construction
Amazon Elastic Compute Cloud, affectionately referred to as "EC2", is AWS’s virtual compute offering.
If you need a machine other than your personal computer to run some tasks on, but don’t want to deal with hardware, then EC2 is one of several options.
Digital Ocean would be another option.
It’s fairly easy to launch an instance through the AWS console.
Instance type is important to specify appropriately as it directly impacts how performant the cloud machine will be as well how much money will be burned per hour.
t2.micro (linux) = 0.0116 USD per hour, which equates to
about $8.50 per month.
Warning Let’s say you run a
c3.4xlargeinstance by accident. That will be 0.84 USD per hour, which is about $613 per month. ☠️
.pem formatted key pair
used for SSH-ing into the instance.
The console provides a few helpful instructions.
AWS networking always leaves me feeling lost and inadequate. I’ll report back here when I learn more.
The one important setting to check is:
- Allow SSH traffic from
Though this is not the most secure, the
.pem key requirement
serves as reasonable line of defense against bad actors.
A default security group will likely get auto-created upon
instance launch. It’ll be named something like
Allowing inbound SSH traffic from
0.0.0.0/0 results in an inbound rule like
|Name||Security group rule ID||IP version||Type||Protocol||Port range||Source||Description|