Heavy council dashboard queries keep forcing a municipal Aurora OLTP cluster to larger instance classes. Which architecture change best controls that database cost?
Select an answer to reveal the explanation.
Short Explanation
Don't make the cash register do the year-end audit. Park big council reports on Redshift so Aurora stays sized for transactions, not warehouse scans.
Full Explanation
Separating analytics onto Amazon Redshift prevents oversized Aurora instances driven by columnar-style report scans. Running heavy analytics on the OLTP writer increases contention and forces costly upsizing. Extra Multi-AZ standbys are for HA, not analytic offload. Glacier storage classes do not replace a SQL analytics engine for interactive dashboards.