You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context: The ability to apply rate-limiting or quota limits on a per-project basis
For example, if an API key is leaked, it should not be able to drain the entire quota allocation or run up an infinity spend. I'm not aware of any provider offering this. The concern is that we have high-criticality api keys and low-criticality api keys, and leaking a less-imports but the key should not be able to impact the QoS on a service that is high-criticality.
Running separate accounts could mitigate this, but that implies additional management overheads and complexity, as well as less cost efficiency.
The text was updated successfully, but these errors were encountered:
Context: The ability to apply rate-limiting or quota limits on a per-project basis
For example, if an API key is leaked, it should not be able to drain the entire quota allocation or run up an infinity spend. I'm not aware of any provider offering this. The concern is that we have high-criticality api keys and low-criticality api keys, and leaking a less-imports but the key should not be able to impact the QoS on a service that is high-criticality.
Running separate accounts could mitigate this, but that implies additional management overheads and complexity, as well as less cost efficiency.
The text was updated successfully, but these errors were encountered: