Skip to content

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

Updated on 2026-10-04

DigitalOcean Spaces — connector

Reads CSV, JSON and XLSX files from a DigitalOcean Space (S3-compatible API, access keys, SigV4) and loads them into the Bronze layer; Parquet is recognized and loaded directly.

On this page (15)

Read before: ../conectores.md (state map) and fichas.md (index of the records).


What it is#

Reads CSV, JSON and XLSX files from a DigitalOcean Space (S3-compatible API, access keys, SigV4) and loads them 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#

Bring data from DigitalOcean Spaces 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 subscription overdue, suspended or canceled, the run is blocked.
  • Shutdown: the ingestion run can be temporarily turned off (maintenance or incident). When that happens, the screen indicates that the resource is unavailable at the moment.

Prerequisites#

  • A DigitalOcean Spaces account with access to the data you want to ingest.
  • In the DigitalOcean panel, under API → Spaces Keys, generate a key pair (preferably restricted to the Space, read-only). Provide the Space region (e.g.: nyc3), the Space name and the Access Key / Secret Key pair; the secret is encrypted and never displayed 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 this connection credential 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 go through redaction in every error/log (raw token, URL-encoded and in JSON).

Form fields#

CampoRótuloTipoObrigatórioObservação
regionRegiãotextosimRegião do Space (nyc3, sfo3, ams3, sgp1, fra1, syd1…). O endpoint é derivado: https://<região>.digitaloceanspaces.com.
bucketSpace (bucket)textosim—
prefixPrefixo / pastatextonãoCada subpasta vira uma tabela; arquivos irmãos viram partições da mesma tabela.
accessKeyIdAccess Keytextosim—
secretAccessKey 🔒Secret Keypassword/secretsimsegredo (cifrado; cofre externo opcional)

Step-by-step#

  1. In the menu Dados → Conexões, use Nova conexão.
  2. Choose DigitalOcean Spaces in the catalog.
  3. Fill out the form fields (see table above).
  4. Use Testar conexão. The result comes separated into 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/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).
  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 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 are masked):

text
# 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 contents of those files appear in the Bronze layer of your workspace, ready for the pipeline.

Limits and costs#

  • Pagination: hard limit per run (default 10,000 pages / 5,000,000 rows); loop-guard.
  • 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#

  • 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 written. The external credential vault is optional and attached per connection; without it the encrypted value stays 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 — the credential for this connector 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 — 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 problems before scheduling.
  • Monitor the runs in the connector observability (error rate, p50/p95, freshness).
  • A schema change at source is signaled by schema drift (new column = info; removed column/type changed = attention).

Related#


Last revision: 2026-10-04. Record automatically generated from the product's connectors catalog.

Related links