- 最新
- 投票最多
- 评论最多
More than likely it is a routing issue. I would first make sure that the VPC the DB instance resides in has an internet gateway attached to it. If it does, there could be a route missing or configured incorrectly (ingress most likely).
Here is a post on how to troubleshoot VPC routing:
https://repost.aws/knowledge-center/troubleshoot-vpc-route-table
Be cautious about having databases in public subnets opening ports to everyone.
Thought convenient it can be maliciously exploited. Consider this: https://aws.amazon.com/blogs/database/securely-connect-to-an-amazon-rds-or-amazon-ec2-database-instance-remotely-with-your-preferred-gui/
Yes I know it and I strongly agree with that, I´m just trying to discover the reason of this problem. Anyway thanks for your advertisement, I'm aware of that.
相关内容
AWS 官方已更新 3 年前- AWS 官方已更新 3 年前
That was exactly the issue, thanks a lot my friend. Very good job helping me, I really own you a favor lol, so thanks again and again and again.