Read first:
../conectores.md(state map) andfichas.md(index of fichas).
What it is#
Reads CSV, JSON and XLSX files from a Wasabi bucket (S3-compatible API, access keys, SigV4) and loads into the Bronze layer; Parquet is recognized and loaded directly.
Supported ingestion modes:
- Nós buscamos — Nós buscamos os dados na sua fonte.
What it's for#
Bringing Wasabi data into your datalake and making 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 included in all plans; the limit is the number of sources allowed by the plan).
- Access: requires an active workspace — with the subscription overdue, suspended or canceled, the run is blocked.
- Shutdown: the ingestion run can be temporarily disabled (maintenance or incident). When that happens, the screen reports that the feature is currently unavailable.
Prerequisites#
- A Wasabi account with access to the data you want to ingest.
- In the Wasabi console, under Access Keys, create an access key pair (preferably from a subuser with read-only policy on the bucket). Provide the bucket region, the bucket name and the Access Key / Secret Key pair; the secret is encrypted and never shown again.
Credentials#
Authentication method: API Key generated in the provider panel, sent in header/parameter.
Sensitive fields. They are encrypted (AES-256-GCM) and are never stored in the connection config, pipeline definition, export or DAG. By default the encrypted value is stored in the database; moving the credential of this connection to an external credential vault is an explicit choice, made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.
- Secret Key (
secretAccessKey)
Secrets are never re-displayed and are redacted in any error/log (raw token, URL-encoded and in JSON).
Form fields#
| Campo | Rótulo | Tipo | Obrigatório | Observação |
|---|---|---|---|---|
region | Região | texto | não | padrão: us-east-1; Região do bucket (us-east-1, us-east-2, us-west-1, eu-central-1, sa-east-1…). O endpoint é derivado: https://s3.<região>.wasabisys.com. |
bucket | Bucket | texto | sim | — |
prefix | Prefixo / pasta | texto | não | Cada subpasta vira uma tabela; arquivos irmãos viram partições da mesma tabela. |
accessKeyId | Access Key | texto | sim | — |
secretAccessKey 🔒 | Secret Key | senha/segredo | sim | segredo (cifrado; cofre externo opcional) |
Step by step#
- In the menu Dados → Conexões, use Nova conexão.
- Choose Wasabi in the catalog.
- Fill in the form fields (see table above).
- Use Testar conexão. The result is shown across three capabilities, each with OK, Failed, Not applicable or Not tested. In this ficha they mean: Network — the object storage endpoint is reachable from the application server; Authentication — the credential in the form (access key or service account, not username/password) was accepted; Read — it was possible to list the objects in the bucket/container under the provided prefix (the displayed count is of visible objects, not of tables).
- Use Salvar conexão. Saving DOES NOT start any ingestion.
- 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.
- In the review, Publicar (agenda desligada) creates version 1 without running anything. Afterwards, Ativar agenda and Executar agora are separate actions.
Example — connection test#
Sample configuration (all values are fictitious; secrets appear masked):
# Exemplo sintético (valores fictícios — não são credenciais reais)
region = us-east-1
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 ceiling per run (default 10,000 pages / 5,000,000 rows); anti-loop safeguard.
- SaaS load: default
batchSize5,000,maxRows200,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#
- Scope by workspace: each customer reads and writes only to their own datalake (
<prefix>_bronze/_silver/_gold); there is never leakage between workspaces. - Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being stored. The external credential vault is optional and enabled per connection; without it the encrypted value remains in the database. Changing the value here DOES NOT revoke the credential at the source.
- Redaction: all errors/logs go through secret redaction (raw, URL-encoded and in JSON).
- Production doesn't fake: a path that would hit mock triggers production guard (explicit failure instead of simulating success).
Common errors#
- Authentication failed — this connector's credential is NOT username/password: it's an access key (or service account). Check the pair provided in the form and whether it is still active in 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 nonexistent or empty — verify the exact bucket name and prefix (folder). A prefix with no objects returns zero visible objects, not an error.
- File in unsupported format — object storage transports files; the pipeline must be able to read the content (CSV, JSON or Parquet). An object in another format is ignored or fails the load, according to 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 changed = attention).
Related#
../conectores.md— connector catalog by state../ingestao-incremental-backfill.md— full, incremental by watermark, backfill and checkpoint../pipeline-medalhao.md— Bronze/Silver/Gold layers and quality../agendamento-retry-dlq.md— scheduling, retry/backoff and DLQ../custo-limites-seguranca.md— cost, ceilings and workspace security
Last review: 2026-10-04. Ficha generated automatically from the product's connector catalog.