Accessing EC2 when browsers are denied

Just check The Root volume associate with your Ec2 machine increase the Throughput and Iops Of that root Volume . For Temporary remove the domain from your domain provide to not send the traffic to machine stop the virtual machine restart again .Once you increase the Iops Throughput you will able to ssh the machine.

If your EC2 instance suddenly became inaccessible from both browsers and SSH (PuTTY), here's how to troubleshoot and regain access without paid support:

The Core Issue:

Sudden loss of both web and SSH access usually means either the instance crashed, security settings changed, or services stopped running.

Step 1: Check Instance Health in EC2 Console

1. Go to EC2 Console and check your instance:

   • Instance State should show "running"
   • Status Checks - look for 2/2 passed (if failing, this shows the problem)

2. View diagnostic information:

   • Actions → Monitor and troubleshoot → Get system log (shows boot and system messages)
   • Actions → Monitor and troubleshoot → Get instance screenshot (shows what's on the screen)

These logs often reveal exactly what failed (crashed service, disk full, kernel panic, etc.)

Step 2: Regain Console Access Without SSH

Use AWS Systems Manager Session Manager as an alternative to SSH/PuTTY:

1. Go to Systems Manager → Session Manager → Start Session
2. Select your instance from the list
3. Click "Start session"

This works if your instance has:

• SSM agent installed (pre-installed on Amazon Linux 2/2023, Ubuntu 16.04+, Windows Server 2016+)
• IAM role attached with AmazonSSMManagedInstanceCore policy

If Session Manager shows your instance, you can connect without SSH and investigate.

Step 3: Once Connected, Check What's Running

   sudo systemctl status apache2   # or httpd/nginx
   sudo systemctl status mysql      # or mariadb/postgresql
   sudo df -h                       # check disk space
   sudo top                         # check CPU/memory
   sudo journalctl -xe              # check system logs

Common causes:

• Services didn't restart after a reboot
• Disk full (100% usage prevents services from starting)
• High CPU/memory causing system freeze

Step 4: Restart Failed Services

   sudo systemctl start apache2     # or your web server
   sudo systemctl start mysql       # or your database
   sudo systemctl enable apache2    # ensure it starts on boot
   sudo systemctl enable mysql

Step 5: Simple Reboot (If Session Manager Doesn't Work)

From EC2 Console: Actions → Instance State → Reboot

This often fixes temporary freezes and is safe (no data loss).

Step 6: Verify Security Group Settings

Check if security group rules were accidentally changed:

• Port 22 (SSH) should allow your IP address
• Port 80/443 (HTTP/HTTPS) should allow 0.0.0.0/0
• Check Network ACLs as well

If Nothing Works - Last Resort:

1. Stop the instance (don't terminate)
2. Create a snapshot of the root volume (for backup)
3. Start the instance again (forces new host hardware)

Or detach the root volume, attach to another instance, and recover your data/fix configuration.

Getting Free Support:

You don't need paid support ($30/month) for this:

• AWS re:Post (where you're posting now) - free community support
• AWS Support Center - even free tier accounts can open account/billing inquiries
• AWS Health Dashboard - check for regional service issues

Start with the system log and instance screenshot - they usually show exactly why it stopped responding.

Relevant Documentation:

• Troubleshoot instance connectivity: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html
• Systems Manager Session Manager: https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html
• View system logs: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-console.html

Do you have access to AWS console? What is the status of your EC2 instance?

It seems the problem was with AWS server, once started to behave we were able to access with Putty and restart the application. This time the server was not operating for long time.

When an EC2 instance suddenly becomes inaccessible from both web browsers and SSH (PuTTY), it usually does not mean the server is permanently lost. In many cases, the issue is related to instance status or networking rather than a complete failure.

First, check in the EC2 console whether the instance is still in a Running state and review the System Status Check and Instance Status Check results. If either check is failing, a reboot or stop/start often resolves OS-level issues.

If the instance is running normally, review the security group rules to confirm that SSH (port 22) and any required application ports are still allowed from your IP address. Also verify that the route table and network ACLs have not been modified, as changes there can block all inbound access.

Another common cause is a public IP address change after a stop/start. Make sure you are connecting to the current public IP, or consider using an Elastic IP to avoid this in the future.

If SSH access is still unavailable, try AWS Systems Manager Session Manager or EC2 Instance Connect (if previously configured), which allows access without relying on network ports.

As a last resort, you can detach the root EBS volume, attach it to another EC2 instance, and fix configuration or log issues directly. This recovery approach does not require a paid AWS support plan.

In most cases, these steps are sufficient to restore access without involving AWS Support. 번역