Follow-up to #3368, which set up access to the OpenTelemetry Cloudflare account so we could host an OTel Collector for opentelemetry.io. The work lives in open-telemetry/opentelemetry-website-infra.
R2 Object Storage is not enabled on the account. Listing buckets returns:
HTTP 403
{
"success": false,
"errors": [
{ "code": 10042, "message": "Please enable R2 through the Cloudflare Dashboard." }
]
}
I'd like to check whether we can enable it.
What we need it for
- Terraform remote state. We manage the Edge policy in front of the Collector as Terraform, and the state file can't live in the repository. R2 works as an S3-compatible backend.
- Backend storage. The Backends behind the Collector (Prometheus, Jaeger, OpenSearch) write long-term data and snapshots to S3-compatible object storage.
R2 includes 10 GB-month of storage at no cost, then $0.015/GB-month, and charges nothing for egress. The Terraform state is a few hundred KB. The Backends can grow, and we'll size them when we stand them up.
/cc @austinlparker @trask @chalin @svrnm @jaydeluca @maryliag
Follow-up to #3368, which set up access to the OpenTelemetry Cloudflare account so we could host an OTel Collector for opentelemetry.io. The work lives in open-telemetry/opentelemetry-website-infra.
R2 Object Storage is not enabled on the account. Listing buckets returns:
I'd like to check whether we can enable it.
What we need it for
R2 includes 10 GB-month of storage at no cost, then $0.015/GB-month, and charges nothing for egress. The Terraform state is a few hundred KB. The Backends can grow, and we'll size them when we stand them up.
/cc @austinlparker @trask @chalin @svrnm @jaydeluca @maryliag