Resources, Articles, Tricks, and Solutions in connection to AWS

Plesk Services on an Amazon Lightsail Instance - How to Open Access ?

This article covers how to allow access to Plesk Services on an Amazon Lightsail Instance. By default, on Plesk instances on Amazon Lightsail all outgoing connections are allowed, and all incoming connections are blocked. Exceptions are made for connections to ports listed below.

Service name and Ports used by the service:

  • SSH (secure shell) server: TCP 22
  • Web server: TCP 80, TCP 443, TCP 8443, and TCP 8447
  • DNS: TCP 53 and UDP 53

Read More


AWS RDS parameter group max_allowed_packet - How to Modify the parameter ?

This article covers how to create and modify the AWS RDS parameter. 


What is max_connect_errors parameter ?

This parameter indicates how many connection errors are possible before the server blocks a host. If more than max_connect_errors successive connection requests from a host are interrupted without a successful connection, the server blocks that host from further connections. The default value is 100 and can be tuned to your security requirements and environment.

For example, if max_connect_errors=5000, after 5,000 connection requests from Host X are interrupted you get an error like the following:

Host X is blocked because of many connection errors ()

You can simply Unblock the host using the following command:

mysql> flush hosts;
mysql> show global variables like 'max_connect_errors';

+| Variable_name      | Value |
+--------------------+-------+
| max_connect_errors | 5000|
+--------------------+-------+

1 row in set (0.00 sec)

Read More


ec2 key permission denied – "Authentication failed, permission denied"

This article covers method to fix the error, ec2 key permission denied. 

"Permission denied (publickey)" and "Authentication failed, permission denied" errors occur if:

  • You're trying to connect using the wrong user name for your AMI.
  • The permissions are incorrect on the instance.
  • The incorrect SSH public key (.pub) file is in the authorized_keys file.


To fix this error, simply:

  • Verify that you're using the correct user name for your AMI.
  • Also Verify that the instance's permissions are correct and that the correct SSH public key is in the authorized_keys file.

Read More