An alarm on the Aurora PostgreSQL FreeLocalStorage metric indicates the production database is low on temporary space. The administrator finds a weekly report consumes most of the temp storage. What is the appropriate action to address the temporary storage contention caused by the report?

Adding an Aurora read replica and running the report against it is the most appropriate action. This offloads the resource-intensive report queries from the primary instance, preventing it from consuming temporary storage needed for production operations. The read replica will handle its own temporary storage requirements without impacting the primary database. Enabling query plan management might optimize some queries but won't fundamentally address the large temporary storage consumption of a specific report. Storage autoscaling on the DB cluster is for persistent storage, not temporary storage used during query execution. Increasing the DB instance class might provide more memory, which can reduce temporary storage usage by allowing more operations in memory, but it's a more expensive and less targeted solution than offloading the report.