Cannot access Amazon EC2 instance after changing sshd_config file (deadlock)
I was trying to access Amazon EC2 instance without using keypairs (I was doing some tests with Dreamweaver) So, I had a marvelous ideia of changing sshd_config file. sudo nano /etc/ssh/sshd_config And I change the PasswordAuthentication line to: Match User ubuntu PasswordAuthentication yes After restarting I got a sad surprise. I cannot access my machine anymore. And even worst I had only one user (ubuntu) on this instance. My question is: How can I back to original setting ( roolback sshd_config file) if I cannot access my terminal?
Loosing access to an Amazon EC2 instance is a common encounter - how to approach this situation when you don't know the reason yet is addressed in Eric Hammond's excellent summary Solving: "I can't connect to my server on Amazon EC2". However, since you already now that the problem is permission related, you can apply his respective instructions Fixing Files on the Root EBS Volume of an EC2 Instance right away, see my answer to the related question Fixing Amazon EC2 Permissions for a short summary of this approach. Good luck!
Trying to Access Ec2 Got Error Public Key
AWS CloudSearch Filter on non-indexed field
In an AWS CloudFormation template, how can I place an EC2 instance in the subnet determined by a Spot Fleet?
AWS Lambda and zip upload from S3
Chat App on AWS: EC2 (eJabberd XMPP) vs RDS (Relational Database) vs other options? [closed]
In what scenario , the No-VPC option available while creating a DB-Instance Through Amazon RDS. Under Network and Security Option
Configuring HTTPS on elastic beanstalk (single instance) of Tomcat
Aggregation by a compound field (copy_to) not working on Elasticsearch
AWS - How to Connect Elastic Beanstalk to Private RDS Instance
distcp: How to avoid flattening dir if there's only one file in hdfs to s3 copying
AWS billing with python
Is there a substantial delay in operationalization when pointing Route 53 purchased DNS to Elastic IP & EC2 instance
amazon-ecs-agent is always restarting
IAM Roles and instance profile
launch a shell script from lambda in aws
Elastic beanstalk automatically creates a security group that allows all traffic on port 80. How can I disable this?