i have existing AWS RDS instance which is old created on back in 2016.
got the hostname and password my-db-name.XXXXXXXXXXXX.us-west-2.rds.amazonaws.com.
I tried connect to EC2 to access that database (Screenshot below)
screenshot
When i tried to connect, i'm facing the error as follows
Error Message
After # symbol private IP address is different from the EC2 what i seen
so i tried to ping that database hostname(my-db-name.XXXXXXXXXXXX.us-west-2.rds.amazonaws.com) from EC2 via putty and it shows Private hostname which is not related to my private IP EC2.
So i tried again setting Inbound and Outbound security settings to 0.0.0.0 but still same error,
did i missed something?
Related
I have read several stackoverflow posts, but none seem to help.
I want to ssh into my ec2 instance, so I downloaded the private key file as stated in the instructions from aws. After executing "sudo ssh -v -i ubuntu#", my ssh server hangs with no success or failure message.
I made sure my ec2 instance can accept ssh connections and that my private key file does have the correct permissions. Any other debugging steps to resolve this issue ?
When an SSH connection times-out, it is normally an indication that network traffic is not getting to the Amazon EC2 instance.
Things to check:
The instance is running Linux
The instance is launched in a public subnet, which is defined as having a Route Table entry to points to an Internet Gateway
The instance has a public IP address, which you are using for the connection
The Network Access Control Lists (NACLs) are set to their default "Allow All" values
A Security Group associated with the instance that permits inbound access on port 22 (SSH) either from your IP address, or from the Internet (0.0.0.0/0)
Your corporate network permits an outbound SSH connection (try alternate networks, eg home vs work vs tethered to your phone)
See also: Troubleshooting connecting to your instance - Amazon Elastic Compute Cloud
I have created RDS instance with my own VPC. I had selected public accessible while creating the RDS instance. I have attached internet gateway with VPC. The security group for RDS has entry for 3306 port with my system IP address. I am using default ACL. Still on connecting the RDS instance from mysqlworkench error is coming.
Double check that you have added to correct information and test connection from above
image. You also need to open 3306 port for your instance. Check if
you have root user privileges in console.
We have a working AWS RDS instance. But I cannot connect to this database with its proper credentials. The security group has the private ip range from where I'm trying to access.
tracert --> This command returns 'Request timed out' after a 3 hops.
What am I missing?
Note : There are people who can connect to the database already. Somewhere there IP is whitelisted and mine is not?
From AWS RSD click on "VPC security groups" and change the source of the inbound traffice of the associated EC2 to anywhere. Obviously the issue was the security group Source IP address.
Can you please check if the ip address of the machines that can successfully connect and that of your machine lie within the same CIDR configured in the security group ? Also confirm if your local machine has some firewall preventing you from outbound traffic in the specified port ?
I have created an ec2 instance and set the security group such that it is open for all ip but when i try to access the instance via public ip or dns i get the following error :
This site can’t be reached
ec2-xx-xxx-xx-xx.ap-northeast-1.compute.amazonaws.com refused to connect.
My inbound rules :
I've recently setup a VPC on AWS with a EC2 instance and an Aurora RDS. I've assigned security groups and SSH connections with EC2 and connection to RDS seems to work but I cannot authenticate. The error is:
mysql -h <clustername>.cluster-cd00tic6zepk.us-east-1.rds.amazonaws.com -u <master user> -p –P3306
ERROR 1045 (28000): Access denied for user 'xxx'#'10.0.0.104' (using password: YES)
I've also tried connecting via PHP, similar error:
Failed to connect to MySQL: Access denied for user xxx#'10.0.0.46' (using password: YES)
The application server lives on a public subnet and the rds is on a private subnet, not accessible except by the application server... If that makes a difference.
Most of the tutorials and forums show an instance name instead of IP address when connecting to RDS, is this why I can't authenticate? I believe all of the security groups are good because I can connect, is this an issue with Aurora?
In the end I ended up deleting and recreating the RDS instance and everything worked as expected.