Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-04

Cloudflare R2 — connector

Reads CSV, JSON and XLSX files from a Cloudflare R2 bucket (S3 API, API token, SigV4) and loads into the Bronze layer; Parquet is detected and loaded directly.

On this page (15)

Read first: ../conectores.md (state map) and fichas.md (index of specs).


What it is#

Reads CSV, JSON and XLSX files from a Cloudflare R2 bucket (S3 API, API token, SigV4) and loads into the Bronze layer; Parquet is detected and loaded directly.

Supported ingestion modes:

  • We pull — We pull the data from your source.

What it’s for#

Bring data from Cloudflare R2 into your datalake and make it available to the Bronze/Silver/Gold layers, BI models and the natural-language question wizard.

When to use / when not to use#

Use when you need to consolidate this source into the datalake on a scheduled basis, with isolation per workspace.

Remember that the first run with a real credential is followed by our team before the connector is fully released.

Plan and permissions#

  • Plan: core product (connectors are part of all plans; the limit is the number of sources allowed by the plan).
  • Access: requires an active workspace — if subscription is overdue, suspended or cancelled, runs are blocked.
  • Shutdown: ingestion runs can be temporarily disabled (maintenance or incident). When that happens, the UI indicates that the feature is currently unavailable.

Prerequisites#

  • A Cloudflare R2 account with access to the data you want to ingest.
  • In the Cloudflare dashboard, under R2 → Manage R2 API Tokens, create a token with Object Read permission for the bucket. Provide the Account ID (in R2 → Overview), the bucket and the Access Key ID / Secret Access Key pair from the token; the secret is encrypted and never shown again.

Credentials#

Authentication method: API key generated in the provider dashboard, sent in header/parameter.

Sensitive fields. They are encrypted (AES-256-GCM) and are never placed in the config of the connection, in the pipeline definition, in an export or in the DAG. By default the encrypted value is stored in the database; moving the credential from this connection to an external credentials vault is an explicit choice, made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.

  • Secret Access Key (secretAccessKey)

Secrets are never re-displayed and are redacted in every error/log (raw token, URL-encoded and in JSON).

Form fields#

CampoRótuloTipoObrigatórioObservação
accountIdAccount IDtextosimIdentificador da conta Cloudflare (R2 → Overview). O endpoint é derivado: https://<account id>.r2.cloudflarestorage.com.
bucketBuckettextosim—
prefixPrefixo / pastatextonãoCada subpasta vira uma tabela; arquivos irmãos viram partições da mesma tabela.
accessKeyIdAccess Key IDtextosim—
secretAccessKey 🔒Secret Access Keysenha/segredosimsegredo (cifrado; cofre externo opcional)

Step-by-step#

  1. No menu Dados → Conexões, use Nova conexão.
  2. Escolha Cloudflare R2 no catálogo.
  3. Preencha os campos do formulário (veja a tabela acima).
  4. Use Testar conexão. O resultado vem separado em três capacidades, cada uma com OK, Failed, Not applicable ou Not tested. Nesta ficha elas significam: Network — the storage service endpoint is reachable from the application server; Authentication — the credential provided in the form (access key or service account, not user/password) was accepted; Read — it was possible to list the objects in the bucket/container under the provided prefix (the count shown is of visible objects, not of tables).
  5. Use Salvar conexão. Saving DOES NOT start any ingestion.
  6. On the connection card, use Montar extração (or go to Orquestração → Pipelines and use Conectar fonte). The pipeline points to the saved connection — the credential is not copied.
  7. In the review, Publicar (agenda desligada) creates version 1 without running anything. Afterwards, Ativar agenda and Executar agora are separate actions.

Example — connection test#

Example configuration (all values are fictitious; secrets appear masked):

text
# Exemplo sintético (valores fictícios — não são credenciais reais)
accountId = <accountId>
bucket = meu-bucket-exemplo
prefix = dados/2026/
accessKeyId = AKIAEXEMPLOFICTICIO0
secretAccessKey = •••••• (cifrado — nunca exibido)

Expected result#

Testar conexão returns the number of visible objects under the provided prefix. After the first load, the content of those files appears in the Bronze layer of your workspace, ready for the pipeline.

Limits and costs#

  • Pagination: hard cap per run (default 10,000 pages / 5,000,000 rows); loop protection.
  • SaaS load: default batchSize 5,000, maxRows 200,000 per resource.
  • Estimated volume: ~3 GB/month (catalog estimate, not measurement).
  • Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (billable).

Security#

  • Workspace scoping: each client reads and writes only to their own datalake (<prefixo>_bronze / _silver / _gold); there is never leakage between workspaces.
  • Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being written. The external credentials vault is optional and enabled per connection; without it, the encrypted value is stored in the database. Changing the value here DOES NOT revoke the credential at the source.
  • Redaction: every error/log goes through secret redaction (raw, URL-encoded and in JSON).
  • Production does not fake: a path that would fall into a mock triggers the production guard (explicit failure instead of simulating success).

Common errors#

  • Authentication failed — this connector's credential is NOT user/password: it is an access key (or service account). Check the pair entered in the form and whether it is still active at the provider.
  • Listing denied — the credential authenticates but cannot list the bucket. Grant bucket listing and object read under the prefix; read permission without listing is not enough, because the pipeline needs to discover which files exist.
  • Bucket/prefix does not exist or is empty — check the exact bucket name and the prefix (folder). A prefix with no objects returns zero visible objects, not an error.
  • File in unsupported format — object storage transports files; the pipeline needs to be able to read the content (CSV, JSON or Parquet). An object in another format is ignored or fails the load, depending on the pipeline policy.

Troubleshooting#

  • Use Testar conexão to isolate credential/network issues before scheduling.
  • Monitor runs in the observability por conector (error rate, p50/p95, freshness).
  • A schema change at the source is signaled by schema drift (new column = info; removed column/type change = attention).

Related#


Last revision: 2026-10-04. Spec automatically generated from the product connectors catalog.

Related links