Introduction

The main Amazon RDS console shows infrastructure details such as instance status, storage, networking, and backups, but it usually does not act like a full database browser. To inspect actual tables, you typically connect to the database engine with a SQL client, though some AWS console-based query tools exist for certain supported setups.

What The RDS Console Shows

When you open an RDS database in the AWS console, you can see operational metadata such as:

• instance or cluster identifier
• engine type and version
• endpoint and port
• parameter groups and security groups
• monitoring, logs, and backups

Those screens manage the database service, not the schema objects inside the database. That is why many users look for tables in the console and do not find a built-in table tree on the instance details page.

Use A Database Client For Tables

The standard way to view tables is to connect to the database engine directly with a compatible client.

Examples:

• MySQL or MariaDB: MySQL Workbench or the mysql CLI
• PostgreSQL: pgAdmin, DBeaver, or psql
• SQL Server: SQL Server Management Studio

For MySQL, a quick table listing looks like this:

mysql -h your-rds-endpoint -P 3306 -u admin -p

Then inside the SQL shell:

USE appdb;
SHOW TABLES;

For PostgreSQL, the equivalent flow is:

psql -h your-rds-endpoint -U appuser -d appdb

Then:

\dt

These tools show the actual schema because they connect to the engine, not just to the AWS control plane.

Query Editor Cases

AWS also provides query tooling in the console for some supported database setups. When available and properly configured, those tools let you run SQL from the browser instead of opening an external desktop client.

Even then, the table list comes from SQL queries against the database itself rather than from the regular RDS instance overview page. The mental model should remain the same: the console page manages the service, while SQL tools inspect the database contents.

What You Need Before Connecting

To view tables from any client, you need:

• the RDS endpoint and port from the console
• valid database credentials
• network access through the VPC, security group, or tunnel path
• permission on the target database

If the client cannot connect, the issue is usually network or authentication, not the absence of tables.

Example Metadata Query

For engines that support the information schema, you can query table metadata directly.

SELECT table_schema, table_name
FROM information_schema.tables
WHERE table_schema NOT IN ('information_schema', 'mysql', 'performance_schema', 'sys');

This is useful when you want a cross-client, scriptable way to enumerate tables instead of browsing a GUI.

Common Pitfalls

The most common mistake is expecting the RDS instance details page to show a database-object explorer. RDS primarily manages infrastructure, not per-table browsing.

Another mistake is confusing the AWS login with database credentials. Signing into the AWS console does not automatically sign you into the database engine.

A third issue is forgetting network access rules. The endpoint may be visible in the console, but if security groups or private subnets block your client, you still cannot inspect tables.

Summary

• The standard RDS console focuses on instance and cluster management, not table browsing.
• To see tables, connect to the database engine with a SQL client or supported query tool.
• Use the RDS endpoint, port, and database credentials from the instance details.
• Query tools in the console, when available, still inspect tables through SQL rather than through the main instance page.
• If you cannot see tables, check connectivity and permissions before assuming the schema is missing.