Assigned
Status Update
Comments
va...@google.com <va...@google.com>
ja...@google.com <ja...@google.com> #2
Hello,
Thank you for reaching out.
This issue was forwarded to our product team. Please keep in mind that this issue has to be analyzed and considered by the product team and I can't provide you ETA for it to be delivered. However, you can keep track of the status by following this thread.
Kind Regards
Description
For instance: A service takes user videos and submit them to GCP API, a malicious user can upload a bunch long but very small videos, then the service will get unlimitedly billed a lot. There should be a way to stop loss.
Accepting '*' wildcard input uri might not be a good decision, and it is not well-documented. Same reason for preventing mistakes and abuse.
The Cancellation functionality might not working as intended(details below).
Post with some detail:https://www.googlecloudcommunity.com/gc/AI-ML/Suggestion-on-billing-system-quota-of-AI-relative-GCP-APIs/m-p/850483/highlight/true#M10960
Suggestion:
Credit based allocation might be great, you only buy credits you needs. User could choose auto replenish or not.
Library/ Console could be improved for monitoring and control.