Since you are connecting through a SSH tunnel, this means that the MySQL port 3306 from us-east-1.amazonaws.com is being opened locally on your computer. The ip address of your computer is 127.0.0.1 or localhost. When you connect to the mysql server on us-east-1.amazonaws.com, you're actually accessing it via 127.0.0.1, i.e. your computer. If you had another tunnel open, or MySQL running locally on your computer, then it may be that other MySQL server that's rejecting your authentication attempts
There are some tests you can try :
1. What ports is you Windows computer listening on
From a command prompt : netstat -a (lists all the ports that are open)
In linux it would be : netstat -tlpn
2. Basic connectivity test
From a DOS command prompt or linux console : telnet 127.0.0.1 3306
If you get a time out, or some other program responds then your tunnel isn't setup correctly.
3. Change the port number that MySQL Workbench is opening locally
We're assuming that MySQL workbench is creating the tunnel on your computer. If so, in MySQL workbench, try tunneling through another port number like 9000.
Make sure that 9000 wasn't listed as an open port from : netstat -a
If you have ssh access to us-east-1.amazonaws.com
4. Try connecting to MySQL from us-east-1.amazonaws.com
mysql -u myuser -h 127.0.0.1 -p
And as Rolando said, you'll want to verify that you are connecting with the right credentials. For example, if you are connecting as myuser@127.0.0.1 and you have a user myuser without a host, you probably won't be able to connect using user@127.0.0.1.
According to the MySQL Documentation, the steps for the Migration Wizard should be
- Connecting to the databases
- Schemata Retrieval and Selection
- Reverse Engineering
- Object Selection
- Migration
- Manual Editing
- Target Creation Options
- Schema Creation
- Create Target Results
- Data Migration Setup
- Bulk Data Transfer
- Migration Report
Sounds like you got to Step 9. You have to make sure to setup Data Migration. Apparently, it is not automatic.
If you are having problems with the import, you are not alone. This has been a source of heartache for many. You may need to try :
Best Answer
You can see max_allowed_packet to 1G in your session
You can do so because MySQL will not immediately allocate it. A packet can grow. Please note how it mentions this in the MySQL Documentation:
You should go ahead and add max_allowed_packet to
my.cnf
That way it is globally available for all incoming connections when you restart mysql. You don't have to restart mysql right now. You can just run:
Give it a Try !!!