Score:0

Restrict access to IP's exposed through VPN

in flag

We have the following requirement.

A back end service of our app runs in GCP. The application is SaaS and tenants are pooled. So this backend handles requests from multiple tenants. When a request for a particular tenant is processed, the backend service needs to call a set of API's which are exposed by a service that runs in the tenant specific data center. The tenant specific data center is connected to VPC through VPN.

We need to make sure that the SaaS backend can never call an API exposed by tenant 2 while processing a request for tenant 1. Obviously we can enforce this logic as part of application logic, but to be safer it is better if access control can also be provided through infrastructure. How can we do this in GCP without any significant performance drop.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.