I have 2 AWS accounts. Let's say in the Prod account I run a public RDS instance (deployed to a public subnet, with an assigned public IP address).
Now, I would like to access my RDS instance from another AWS account, let's call it Dev account. However, whenever I do a DNS lookup, it resolves to the private IP address of RDS, and since the VPCs (in Prod and Dev accounts) are not peered, I get a connection timeout.
Is there a way I can configure Route53 Resolver to use public NS servers to resolve the RDS's public IP address, and not use the "shortcut"?
I have tried to add a Route53 Resolver rule (in Dev account) with the RDS instance's domain name, set the rule type to System, and associated it with the VPC, from which I connect to RDS (Dev account). However, it still resolves to the private IP address of RDS.
Any thoughts?