Design guardrails to avoid noisy neighbors in a shared multitenant Postgresql DB

Question

We own a shared PostgreSQL DB instance which is currently used by multiple services - each service has their own schema and tables residing under the respective schemas.

The obvious problem with this is one service can keep hogging the entire available IOPS because of some rogue queries. This service then becomes a noisy neighbor and impacts other service performance.

I am looking for ideas in coming up with appropriate guardrails in terms of quotas - e.g. read-quota (limit on blk_read?) and write quota (limit on bytes to be written to disk/sec ?) to prevent services abusing the DB instance.

Any ideas on how can I do this in PostgreSQL without essentially overloading DB performance while collecting these metrics? We have our DB instance hosted on AWS RDS.