We use Aurora MySQL and Aurora PostgreSQL, and ad-hoc queries are restricted to the reader endpoint. That makes it hard to investigate live waits, locks, and query plans on the writer.
Can a reader expose the writer's activity, and what is a safe way to get more detail when it cannot? Also, how useful is an execution plan captured on a reader?
2a!cobaltspoon_763:
So the dashboard can point us toward the writer's problem, but a reader session won't give us the writer's live lock view?
Vexnari.4u:
Right. For live, instance-local details, connect to the affected instance. Check the writer specifically rather than assuming the reader endpoint landed somewhere useful.