2개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
1
You also need to specify the publicly-accessible attribute when creating or modifying the instance.
--publicly-accessible
0
Here is a link to a troubleshooting Document for public RDS accessibility. . . https://aws.amazon.com/premiumsupport/knowledge-center/rds-connectivity-instance-subnet-vpc/
Hope this helps.
답변함 일 년 전
관련 콘텐츠
AWS 공식업데이트됨 10달 전- AWS 공식업데이트됨 2년 전
- AWS 공식업데이트됨 2년 전
Thanks @tedtrent. From the doc, it appears we do need to modify the publicly accessible property. Does this mean that the default behavior depending on DBSubnetGroupName is not supported/valid anymore?
As @philaws mentioned in his answer you may need to add --publicly-accessible when building the RDS instance. This is a security feature on RDS that by default prevents a DNS name resolving to a public IP address, which could expose it to malicious attacks on the Internet. This is a different behavior than with normal EC2 instances. Modifying the database instance's "Public accessibility" parameter in addition to the VPC security group helps restrict unauthorized access. Use caution with unrestricted access over the public internet.