Thanks for the suggestion. Our Strapi API permissions are setup as read-only; we just want to keep all its requests from that region to that region’s Strapi API, which would connect to that region’s DB (which is read only). We can’t even start the Strapi API (using npm run start), since it attempts to make some updates in the DB on startup.
If we could route the DB write requests (updates, inserts, deletes) to the primary DB, and keep all read requests (selects) at the secondary (read-only) DB, that would accomplish our goal. But, I think in order to do that, we’d have to change the core Strapi code (of which we are trying to avoid) - unless someone knows of workaround or approach we have not thought of.
Or is there another way to access the Strapi APIs without using ‘npm run start’ to start those APIs?