Read first:
../conectores.md(state map) andfichas.md(index of datasheets).
What it is#
Reads CSV, JSON and XLSX files from your Amazon S3 bucket (access keys, SigV4) and loads them into the Bronze layer; Parquet is detected and loaded directly.
Supported ingestion modes:
- Nós buscamos — We pull the data from your source.
What it's for#
Bring data from Amazon S3 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.
Avoid sending files with unstable schema without first checking profiling and schema drift.
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 — with the subscription overdue, suspended or canceled, the run is blocked.
- Shutdown: the ingestion run can be temporarily turned off (maintenance or incident). When this happens, the screen indicates the resource is unavailable at the moment.
Prerequisites#
- The source bucket/container, and the prefix (folder) from which objects will be read.
- A credential with permission to list the bucket and read objects under that prefix — that's all. It's not necessary (nor desirable) to grant write, delete or bucket administration.
- Files under the prefix must be in a format the pipeline can read (CSV, JSON or Parquet). Object storage is a transport, not a format: the schema comes from the file.
Credentials#
Sensitive fields. They are encrypted (AES-256-GCM) and never stored in the connection config, in the pipeline definition, in exports or in the DAG. By default the encrypted value is stored in the database; moving this connection's credential 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 any error/log (raw token, URL-encoded and in JSON).
Form fields#
| Campo | Rótulo | Tipo | Obrigatório | Observação |
|---|---|---|---|---|
bucket | Bucket | texto | sim | — |
region | Região | texto | sim | — |
prefix | Prefixo / pasta | texto | não | — |
accessKeyId | Access Key ID | texto | sim | — |
secretAccessKey 🔒 | Secret Access Key | senha/segredo | sim | segredo (cifrado; cofre externo opcional) |
Step by step#
- In the menu Dados → Conexões, use Nova conexão.
- Choose Amazon S3 in the catalog.
- Fill the form fields (see the table above).
- Use Testar conexão. The result is returned separated into three capabilities, each with OK, Failed, Not applicable or Not tested. In this datasheet 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; Reading — 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 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)
bucket = meu-bucket-exemplo
region = us-east-1
prefix = dados/2026/
accessKeyId = AKIAEXEMPLOFICTICIO0
secretAccessKey = •••••• (cifrado — nunca exibido)Expected result#
The Testar conexão returns the count of visible objects under the provided prefix. After the first load, the contents of those files appear 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 lines); anti-loop guard.
- 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 (
<prefixo>_bronze/_silver/_gold); there is never leakage between workspaces. - Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being stored. The external credentials vault is optional and enabled per connection; without it, the encrypted value stays in the database. Changing the value here DOES NOT revoke the credential at the origin.
- Redaction: all errors/logs go through secret redaction (raw, URL-encoded and in JSON).
- Production does not mock: a code path that would fall into 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 read permission for objects under the prefix; read permission without listing is not enough because the pipeline needs to discover which files exist.
- Bucket/prefix nonexistent or 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 must be able to read the content (CSV, JSON or Parquet). An object in another format is ignored or fails during load, depending on the pipeline policy.
Troubleshooting#
- Use Testar conexão to isolate credential/network issues before scheduling.
- Monitor the runs in the observabilidade 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, caps and workspace security
Last review: 2026-10-04. Datasheet generated automatically from the product's connector catalog.