https://docs.aws.amazon.com/cli/latest/reference/opsworks/create-instance.html
Change volume region for attach/mount
https://serverfault.com/questions/869710/is-it-possible-to-change-the-ebs-volume-to-different-availability-zones
GP2 vs IO1 (General Purpose vs I Optimized) AWS EBS SSD
https://www.fittedcloud.com/blog/is-it-possible-to-use-ebs-gp2-instead-of-io1-achieve-same-performance-and-save-50/
I can not access new Instance by normal SSH. After copy guide from control panel as bellow I can login. Latter I realize that I have used wrong user ('ec2') instead of ubuntu. (old but often miss this point).
From guide I see that there are public DNS, then I can use this to connect.
Ping often disabled by default on EC2 instance.
To access your instance:
Open an SSH client. (find out how to connect using PuTTY)
Locate your private key file (osx_key_one.pem). The wizard automatically detects the key you used to launch the instance.
Your key must not be publicly viewable for SSH to work. Use this command if needed:
chmod 400 key_one.pem
Connect to your instance using its Public DNS:
ec2-18-20-18-70.compute-1.amazonaws.com
Example:
ssh -i "key_one.pem" ubuntu@ec2-18-20-18-70.compute-1.amazonaws.com
Please note that in most cases the username above will be correct, however please ensure that you read your AMI usage instructions to ensure that the AMI owner has not changed the default AMI username.
If you need any assistance connecting to your instance, please see our connection documentation.
Close
So many time working with mount
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html
But still notice fstab test for sure that mount not having any problem, otherwise boot will fail.
It is very useful to test fstab mount devices when server still running (after making change) because of error could lead to unable to access machine later.
Change volume region for attach/mount
https://serverfault.com/questions/869710/is-it-possible-to-change-the-ebs-volume-to-different-availability-zones
GP2 vs IO1 (General Purpose vs I Optimized) AWS EBS SSD
https://www.fittedcloud.com/blog/is-it-possible-to-use-ebs-gp2-instead-of-io1-achieve-same-performance-and-save-50/
I can not access new Instance by normal SSH. After copy guide from control panel as bellow I can login. Latter I realize that I have used wrong user ('ec2') instead of ubuntu. (old but often miss this point).
From guide I see that there are public DNS, then I can use this to connect.
Ping often disabled by default on EC2 instance.
To access your instance:
Open an SSH client. (find out how to connect using PuTTY)
Locate your private key file (osx_key_one.pem). The wizard automatically detects the key you used to launch the instance.
Your key must not be publicly viewable for SSH to work. Use this command if needed:
chmod 400 key_one.pem
Connect to your instance using its Public DNS:
ec2-18-20-18-70.compute-1.amazonaws.com
Example:
ssh -i "key_one.pem" ubuntu@ec2-18-20-18-70.compute-1.amazonaws.com
Please note that in most cases the username above will be correct, however please ensure that you read your AMI usage instructions to ensure that the AMI owner has not changed the default AMI username.
If you need any assistance connecting to your instance, please see our connection documentation.
Close
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html
But still notice fstab test for sure that mount not having any problem, otherwise boot will fail.
It is very useful to test fstab mount devices when server still running (after making change) because of error could lead to unable to access machine later.
Comments
Post a Comment