Read before:
../conectores.md(state map) andfichas.md(index of the datasheets).
What it is#
Reads CSV, JSON and XLSX files from a MinIO bucket (S3 API, access keys, SigV4) and loads them into the Bronze layer; Parquet is detected and loaded directly.
Supported ingestion modes:
- Nós buscamos — We fetch the data from your source.
What it's for#
Bring data from MinIO 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 by 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 of the plan).
- Access: requires an active workspace — with overdue, suspended or cancelled subscription, the run is blocked.
- Shutdown: the ingestion run can be temporarily disabled (maintenance or incident). When this happens, the screen indicates that the feature is unavailable at the moment.
Prerequisites#
- A MinIO account with access to the data you want to ingest.
- In the MinIO console, create an access key (Identity → Service Accounts) with bucket read and list policy (s3:GetObject, s3:ListBucket). Provide the server endpoint, bucket and keys; the secret key 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 never remain 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 of this connection to the 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#
| Field | Label | Type | Required | Note |
|---|---|---|---|---|
endpoint | Server endpoint | text | yes | URL of the MinIO S3 API (include port if any). Must be reachable from the internet or via VPN. |
bucket | Bucket | text | yes | — |
prefix | Prefix / folder | text | no | Each subfolder becomes a table; sibling files become partitions of the same table. |
region | Region | text | no | default: us-east-1; Region configured on the server (MINIO_REGION). MinIO's default is us-east-1. |
accessKeyId | Access Key | text | yes | — |
secretAccessKey 🔒 | Secret Key | password/secret | yes | secret (encrypted; external vault optional) |
Step-by-step#
- In the Dados → Conexões menu, use Nova conexão.
- Choose MinIO in the catalog.
- Fill in the form fields (see the table above).
- Use Testar conexão. The result is returned in three capabilities, each with OK, Failed, Not applicable or Not tested. In this sheet they mean: Network — the storage service endpoint is reachable from the application server; Authentication — the credential in the form (access key or service account, not username and password) was accepted; Read — it was possible to list the objects in the bucket/container under the specified 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 executing anything. Afterwards, Ativar agenda and Executar agora are separate actions.
Example — connection test#
Example configuration (all values are fictitious; secrets appear masked):
# Exemplo sintético (valores fictícios — não são credenciais reais)
endpoint = <endpoint>
bucket = meu-bucket-exemplo
prefix = dados/2026/
region = us-east-1
accessKeyId = AKIAEXEMPLOFICTICIO0
secretAccessKey = •••••• (cifrado — nunca exibido)Expected result#
The Testar conexão returns the number of visible objects under the specified 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); contains anti-loop protection.
- SaaS load: default
batchSize5,000,maxRows200,000 per resource. - Estimated volume: ~3 GB/month (catalog estimate, not measurement).
- Cost: the extraction itself is not billed by the platform; the Bronze load consumes datalake processing (billable).
Security#
- Workspace scope: 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 attached 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 does not mock: a path that would fall into a mock triggers the production guard (explicit failure instead of simulating success).
Common errors#
- Authentication failed — the credential for this connector is NOT username and password: it is an access key (or service account). Check the pair provided 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 the runs in connector observability (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, limits and security by workspace
Last review: 2026-10-04. Datasheet automatically generated from the product connector catalog.