[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
howtos:cloud:aws_ec2 [2020/07/05 16:39 (UTC)] – [Snapshot import] bifferoshowtos:cloud:aws_ec2 [2020/07/07 00:49 (UTC)] – [Security] bifferos
Line 18: Line 18:
   - Reboot and ensure you still have access using your private key.   - Reboot and ensure you still have access using your private key.
   - Double-check that you cannot login using the password that would normally work on the VM console for your user.   - Double-check that you cannot login using the password that would normally work on the VM console for your user.
- +<note important>Within an hour of your instance becoming live it will be logging access attempts by Russian hackers. AWS address ranges are scanned regularly for vulnerabilities precisely because so many users screw up their security.  Don't be caught out.</note>
-Of course, how secure your instance is will ultimately be your responsibility, this is just advice.+
  
 ===== Disk Formats ===== ===== Disk Formats =====
Line 79: Line 78:
 ===== Connect to an Instance ===== ===== Connect to an Instance =====
  
-You can now create an instance.  Any instance will do, a t2.micro will have 1 CPU and plenty of RAM to boot Slackware.  Shut down the instance, disconnect it's root drive.  You can delete the root EBS volume supplied with that instance if you want because we'll create another one.  There's no point in paying for anything you don't use.+You can now create an instance.  Any instance will do, a t2.micro will have 1 CPU and plenty of RAM to boot Slackware.  Shut down the instance, disconnect its root drive.  You can delete the root EBS volume supplied with that instance if you want because we'll create another one.  There's no point in paying for EBS storage you don't need.
  
 You can then use the AWS Console to create an EBS volume from your uploaded snapshot, and attach the EBS volume as the root device of your instance.  Make sure you specify the device as /dev/sda, to ensure it will be the root device.  I found this slightly confusing because it's actually /dev/xvda in the running instance but there you go. You can then use the AWS Console to create an EBS volume from your uploaded snapshot, and attach the EBS volume as the root device of your instance.  Make sure you specify the device as /dev/sda, to ensure it will be the root device.  I found this slightly confusing because it's actually /dev/xvda in the running instance but there you go.

Trace:

howtos:cloud:aws_ec2 ()