Possible Implementations multiple projects

1. We will have 1-ClaimAV project with 4-buckets. and other project-x\y where they will have access to unscanned, clean and qaraninet bucked. cloud-computing projects-x-y will attach data to unscan-bucked and with knowing the name will check in clean bucked or quarantined and will copy that file in to the own bucked and delete from claimAV.

what is benefits using this logic: One ClaimAV env we need: * * 5buckeds: 1. clean-e-learning-dev-416612, 2. unscanned-e-learning-dev-416612 3. quarantined-e-learning-dev-416612 4. cvd-mirror-e-learning-dev-416612 5. e-learning-dev-416612_cloudbuild * * Cloud Scheduler, * Eventarc.

But if we use 1 ClaimAV env for 2 projects: we will have 5 buckets, 1-cloud run app, +2 buckets for 2 own projects. In this scenario only 1 concern is data flow. How much files will be for scanning and time with delay.

also the cost