Google cloud storage for backups - multiple instances setup

[NateDoc]

I'm in the process of changing over to Google storage backups for multiple instances, and it seem that to segment access to the storage between instances, a completely new project plus new storage bucket is required for the 3CX instance to work with it. If the service account is limited in any way the instance reports an Invalid JSON error when trying to connect. Is this by design? It would be preferable to reduce the number of projects in our GCP and have only separate service accounts and storage buckets in the main project instead. Maybe I'm overlooking something?

 

[Alphabetic]

You will need to create a new project if you want to seperate them.

 

[NickD_3CX]

Your not overlooking something.

The implementation we have requires the installation to view all buckets, when you click on location it lists all of them, and if it can't it shows an error.

Granted the error is a bit misleading, but to isolate you need to to do what @kieferschild suggested.

 

[NateDoc]

Thanks Nick for the confirmation. I'll just suggest that if it is at all possible in the future to permit segmentation without having to create a completely new project stack in GCP per instance that'd be highly useful. If one were to implement a single project for multiple tenants it is trivial to access all bucket data from each instance, which isn't great from a security standpoint.