- Newest
- Most votes
- Most comments
Hello.
What are the security group's inbound rules configured?
If RDS does not enable public access, access from EC2 to RDS will be private access, so you will not be able to communicate even if you register ElasticIP.
If it is a private connection, please refer to the EC2 private IP address and EC2 security group in the security group in the inbound rule.
https://docs.aws.amazon.com/quicksight/latest/user/vpc-security-groups.html#vpc-inbound-rules
For a instance given INBOUND OUTBOUND AS ALL TRAFFIC STILL ISSUE IS THERE .
For Diffrent server is working fine for a one particular server is not working
WHAT i did is Sub domain taken from one server that pointed to this cpanel public address then domain is working now from old server have one database from that database need to access data its not working but diffrent server is working fine under same account in In motion hosting
ping server also not working but public ip is showing
Maybe we need to clarify your question first. Just Assume your scenario is about connecting to RDS from EC2 from the same VPC, correct me if in need. Based on the information you provided, I have summarized the key points of the issue:
- The cURL function in PHP is not working correctly, but running cURL commands in the console works fine.
- Unable to access a remote MySQL server from cPanel, resulting in a timeout error.
- The server is pingable, but the connections still fail.
Possible reasons and troubleshooting steps:
- security group setting a. ensure the outbound rule allow 3306 port to RDS instance; you can configure a rule that allow access to the security group of rds;
- PHP environment configuration (Most likely the root cause in this case) a. Verify that the cURL extension is correctly installed and enabled in PHP. b. Check the PHP connection timeout settings.
- MySQL configuration a. make sure the inbound rule of RDS MySQL allows access from EC2, you can also configure a inbound rule to allow access from the security group of EC2; you can also refer to the following docs to identify the root cause in your case .
- https://repost.aws/knowledge-center/rds-cannot-connect
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Troubleshooting.html
I hope you found this helpful. If you face any other issues or require further assistance, you could also reach out to AWS Support along with your use case details, and we would be happy to assist you further. Thank you!
im connecting from with AWS to non aws server for database
Relevant content
- asked 7 years ago
- asked 2 years ago
- asked 7 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
