Read-only AWS RDS Postgres evidence collection
AWS RDS audit
AWS RDS Postgres audit
Database Optimization Tool reviews AWS RDS PostgreSQL evidence with clear boundaries around rds_superuser, managed parameters, and extension access.
Local collector runs from your environment
Human review before production decisions
No database changes applied by Database Optimization Tool
What an RDS read-only review can still verify
An AWS RDS Postgres audit should respect managed-role boundaries while still finding query pressure, index waste, bloat risk, and maintenance gaps from PostgreSQL-visible evidence.
Environment limits
RDS exposes rds_superuser rather than full host control. Parameter groups, extension settings, logs, and OS metrics may require separate AWS access outside this read-only audit.
Why EXPLAIN and parameter review stay manual
The collector can read catalog statistics, relation and index size, scan counts, dead tuple signals, vacuum age, and pg_stat_statements when allowed.
What this page cannot promise
Database Optimization Tool does not modify parameter groups, install extensions, create indexes, or claim access to AWS-only telemetry.
Related topics
RelatedLinks for neighboring audit problems
Use these focused guides to compare query pressure, index decisions, and maintenance signals before you change production.
FAQ
Frequently asked questions
These answers stay inside the current Database Optimization Tool product boundary: read-only collection, evidence-gated findings, and human-reviewed next steps.
Does an RDS audit require superuser?
No. A read-only role is preferred. Some evidence may require grants to statistics views, and missing superuser access is called out as a limit.
What if pg_stat_statements is unavailable on RDS?
The audit can still review catalog, index, table, and vacuum evidence. Query-level findings are more limited without pg_stat_statements.
Will Database Optimization Tool change my RDS production database?
No. It does not apply database changes, create indexes, modify parameter groups, or call AWS APIs from this read-only audit path.
When should I read /docs/collector or /sample-report?
Read /docs/collector before preparing RDS evidence, and review /sample-report to see how manual EXPLAIN, parameter context, and permission limits are shown.