S3 Tables (parlel emulator)

A zero-dependency, in-process fake of Amazon S3 Tables (Iceberg table buckets).

PropertyValue
Port4727
ProtocolREST/JSON
HealthcheckGET /_parlel/health
ResetPOST /_parlel/reset

Default connection

AWS_REGION=us-east-1
AWS_ENDPOINT_URL=http://127.0.0.1:4727
AWS_ACCESS_KEY_ID=parlel
AWS_SECRET_ACCESS_KEY=parlel

Supported operations / paths

OperationPath
CreateTableBucketPOST /table-buckets
ListTableBucketsGET /table-buckets
GetTableBucketGET /table-buckets/{arn}
DeleteTableBucketDELETE /table-buckets/{arn}
CreateNamespacePUT /namespaces/{tableBucketARN}
ListNamespacesGET /namespaces/{tableBucketARN}
CreateTablePUT /tables/{tableBucketARN}/{namespace}
ListTablesGET /tables/{tableBucketARN}/{namespace}
GetTableGET /get-table/{tableBucketARN}/{namespace}/{name}

SDK example

import { S3TablesClient, CreateTableBucketCommand } from "@aws-sdk/client-s3tables";

const s3t = new S3TablesClient({
  region: "us-east-1",
  endpoint: "http://127.0.0.1:4727",
  credentials: { accessKeyId: "parlel", secretAccessKey: "parlel" },
});

const { arn } = await s3t.send(new CreateTableBucketCommand({ name: "lake" }));

Access via MCP / preview URL

Reachable through the parlel pool MCP bridge and preview URL. No auth setup required.

Surface coverage

This emulator faithfully replicates the API surface most application code and agents exercise. Anything below the supported lines is either an intentional design choice for a fast, zero-cost local emulator (✓ By design) or a candidate for a future release (⟳ Roadmap) — never a silent inaccuracy.

Legend: ✅ fully supported · ◐ accepted (stored, not strictly enforced) · ✓ by design · ⟳ on the roadmap.

AreaLimitation
IcebergTable metadata is recorded; no actual Iceberg files written.
DataNo row-level read/write; control-plane catalog only.
MaintenanceCompaction/snapshot management is not modeled.
PoliciesBucket/table policies are not enforced.
<!-- parlel:testenv:start -->

Configuration — test.env

Copy these into your test.env (used by the bridge sidecar flow). Tokens are Parlel's seeded test credentials — any non-empty value is accepted by the emulator, so you rarely need to change them. Swap in real credentials only when pointing at the live service in prod.env.

AWS_ACCESS_KEY_ID=parlel
AWS_SECRET_ACCESS_KEY=parlel
AWS_REGION=us-east-1
AWS_ENDPOINT_URL=http://parlel-bridge:4727
<!-- parlel:testenv:end -->