Explore information related to aws error


AWS ERROR 2003 (HY000): Can't connect to MySQL server - Fix it Now ?

This article covers methods to tackle AWS "ERROR 2003 (HY000): Can't connect to MySQL server" for our customers.

You can easily fix this issue by adding the public ip address of my EC2 server to the DB security group default policy.

You can create a new security group with the corresponding IP range/subnet of your EC2 instances(s). You can use the exact IP(s), or use your VPC's subnet(s) as the range.

Once created, you can right click your RDS instance in the management console and select 'Modify'. From there, you can change the associated security groups.

Read More



AWS S3 403 Forbidden Error - Fix it Now ?

This article covers methods to fix HTTP 403 Forbidden error for our customers. 

To troubleshoot the HTTP 403 Forbidden error from the Amazon S3 console, check the following:

  • Missing permissions to s3:PutObject or s3:PutObjectAcl.
  • Missing permissions to use an AWS Key Management Service (AWS KMS) key.
  • Explicit deny statement in the bucket policy.
  • Bucket access control list (ACL) doesn't allow the AWS account root user to write objects.
  • AWS Organizations service control policy doesn't allow access to Amazon S3.

Read More



AWS MySQL error 10060 – Can't connect to MySQL server ?

This article covers methods to resolve AWS MySQL error 10060. This error is a result of the inbound connection rule set on your DB instance.

For each RDS database instance we create, there are Inbound & Outbound connection-security groups.

In AWS RDS console, under 'Databases', click on the 'DB Identifier' of your RDS instance. Then in the 'Security group rules' section, click on 'Inbound' type security group and edit the inbound rule to allow appropriate inbound connections.

You get 3 options here, under 'source' column:

  • Custom.
  • Anywhere (Allows connections from any IP. Not recommended for production.).
  • My IP (Automatically detects your machine's IP).

Read More



AWS Instance loses network connectivity - Fix this issue now

This article covers method to fix AWS Instance loses network connectivity error.

Basically, AWS Instance loses network connectivity if the instance has the wrong time set.


To fix Amazon EC2 Windows instance network connectivity issue:

You can create a temporary elastic network interface, and attach the network interface to the Amazon EC2 Windows instance. Then, you can  temporarily connect to the instance and fix the issue.

1. Open the Amazon EC2 console, and then choose Instances from the navigation pane.

2. Select your instance. From the Description tab, note the Subnet ID.

3. Create a new network interface in the same subnet as the instance.

Important: Be sure to select a security group that allows incoming Remote Desktop Protocol (RDP) traffic from your IP address.

4. Attach the new network interface to the instance.

Note: The network interface might take a few minutes to come online. If you connect to the instance using RDP, associate an Elastic IP address with the network interface.

5. Using the new network interface, connect to the instance using RDP.

6. Change the network connection settings in Windows to use DHCP. Or, specify the correct private IP address settings. For instructions, see Configuring a secondary private IPv4 address for your Windows instance.

7. Detach the temporary network interface.

Note: If you've associated an Elastic IP address with the network interface, and no longer need the Elastic IP address, release the Elastic IP address.

Read More



AWS error code 0x204

This article will guide you on methods to fix AWS #error code 0x204 which happens in the process of trying to login to a remote machine on VPC.

Amazon Virtual Private #Cloud (Amazon #VPC) is a service that lets you launch AWS resources in a logically isolated virtual network that you define. You can use both IPv4 and IPv6 for most resources in your virtual private cloud, helping to ensure secure and easy access to resources and applications.


To enable RDP access on AWS instance:

i. Open the Amazon EC2 console , set it to the stack's region, and choose Security Groups from the navigation pane. 

ii. Choose AWS-OpsWorks-RDP-Server, choose the Inbound tab, and choose Edit. 

iii. Choose Add Rule and specify the following settings: Type – RDP.


To connect from the #Amazon EC2 console:

1. Open the Amazon #EC2 console.

2. In the left navigation pane, choose Instances and select the instance to which to connect.

3. Choose Connect.

4. On the Connect To Your Instance page, choose EC2 Instance Connect (browser-based SSH connection), Connect.

Read More




For Linux Tutorials

We create Linux HowTos and Tutorials for Sys Admins. Visit us on LinuxAPT.com

Also for Tech related tips, Visit forum.outsourcepath.com or General Technical tips on www.outsourcepath.com