MySQL on Amazon RDS

Amazon RDS for MySQL is ordinary MySQL with the host, backups and failover managed by AWS. It is the same server, so AddisDB connects with its MySQL driver on port 3306 and treats it exactly like a self-hosted instance.

Who it is for

RDS suits teams who want MySQL without operating it. You lose SUPER and file-system access; you gain automated backups, point-in-time recovery, managed minor-version upgrades and read replicas.

The missing SUPER privilege is the one thing that surprises people. A few administrative statements are refused, and the master user RDS creates is a normal account with a broad grant rather than a true superuser. Anything AddisDB does that needs more than that will get MySQL’s own refusal, verbatim.

Aurora MySQL is a different product with its own storage layer and its own entry in the picker. If your endpoint contains cluster-, use Aurora MySQL instead.

Set up the instance

1. In the RDS console open the instance and copy the endpoint, e.g. mydb.abc123.us-east-1.rds.amazonaws.com.
2. Confirm the port, 3306 unless you changed it.
3. Check that the instance is publicly accessible or that you are inside its VPC — this is the usual cause of a timeout.
4. Allow inbound TCP 3306 from your address in the attached security group.
5. Note the master username, which defaults to admin on RDS rather than root.

mysql -h mydb.abc123.us-east-1.rds.amazonaws.com -P 3306 -u admin -p -e 'SELECT VERSION();'

Connect from AddisDB

1. New Connection → MySQL (Amazon RDS). Port prefills to 3306 and username to admin.
2. Paste the endpoint into Host and enter the master credentials.
3. Set SSL mode to require. To verify rather than just encrypt, download the AWS regional CA bundle, select it as the CA certificate, and use verify-full.
4. Test, then Save.

What AddisDB gives you

The full MySQL toolset: schema tree, in-grid editing, structured create and alter table, database-user management, mock data, and query plans through EXPLAIN FORMAT=JSON.

The Live Monitor is real — it reads information_schema.processlist for live sessions and table sizes, and KILL works for cancelling or ending a session, subject to your grant.

Statement statistics come from performance_schema, which RDS enables by default on most instance classes. If the profile view comes back empty, check the performance_schema parameter in your parameter group.