Does Tigris charge for 403/Unauthorized bucket access request?
I know Tigris offers that they can cut down the bill in case of an attack, but I’d still like to know if requests that result in a 403, for example, are billed to the user. Here’s an example: scenario.
Also, to clarify on the egress pricing, what are the minority cases you mean when you say:
I’d like to know if I have services within fly.io and Azure, whether a request from Azure Functions will incur an egress fee. It just seems unclear with that statement, and I don’t want a surprise bill since I’m comparing using Tigris with Cloudflare R2 (which, from calculations, appears cheaper than Tigris and Linode/Akamai).
Also, to clarify on the egress pricing, what are the minority cases you mean when you say:
we don’t charge for regional data transfer, region‑to‑region data transfer, or data transfer out to the internet (egress) in the majority of use cases
I’d like to know if I have services within fly.io and Azure, whether a request from Azure Functions will incur an egress fee. It just seems unclear with that statement, and I don’t want a surprise bill since I’m comparing using Tigris with Cloudflare R2 (which, from calculations, appears cheaper than Tigris and Linode/Akamai).
Solution
We consider this another form of attack, so we won’t bill the user for 403.
Regarding the egress billing, the docs talk about extraordinary bandwidth requirements, which are generally in the PB per month range.
Regarding the egress billing, the docs talk about extraordinary bandwidth requirements, which are generally in the PB per month range.
