Mysql – Create t2 instance and connect via Wokrbench

amazon-rdsMySQL

I've created an t2 RDS instance inside a VPC. The instance is set to Publicly avaiable: No. I wasn't able to connect to the instance using MySQL Workbench. Is there an option to connect to the instance in that state?

I also tried to create with Publicly available: Yes, but I get the following error upon creation:

Cannot create a publicly accessible DBInstance because customer VPC does not support DNS resolution and/or hostnames.

How can I solve this? — I want to be able to create a database in t2 and connect to a t2 RDS instance from Workbench.

Best Answer

customer VPC does not support DNS resolution and/or hostnames.

A quick search for the error message uncovers what it means: your VPC (Amazon Virtual Private Cloud) is not configured to support DNS resolution and/or hostnames, both of which are required to make an RDS instance inside VPC publicly accessible.

The solution appears to be to configure the VPC with these capabilities enabled, after, of course, considering why they might have been disabled to begin with.

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-dns.html

https://forums.aws.amazon.com/thread.jspa?threadID=153914

Related Solutions

Mysql – Connecting to AWS RDS DBInstance with MySQL workbench

If you have instantiated a MySQL RDS Instance, you want to create a DB Security Group

First Create a DB Security Group
Under "Security Group Details", set one of the following connection types
- CIDR/IP
- EC2 Security Group
Assign Address/Mask
Make sure you do not have a proxy/firewall causing interference

MySQL remote connection: Public vs. private IP address

The explanation here is a straightforward one: You can't bind a listening socket to an IP address that your machine's IP stack isn't aware of.

In AWS (whether EC2 Classic or EC2/VPC) as in many network environments these days, your external IP is not configured in your machine -- it's mapped through an external device (router, firewall) to your machine's private IP via NAT (network address translation).

You can confirm that your server itself has no idea about the external IP:

 $ ifconfig

The simplest solution, of course, is binding to 0.0.0.0 unless you have a specific reason not to.

http://en.m.wikipedia.org/wiki/Network_address_translation

Best Answer

Related Solutions

Mysql – Connecting to AWS RDS DBInstance with MySQL workbench

MySQL remote connection: Public vs. private IP address

Related Question