OpenSearch (parlel emulator)

A zero-dependency, in-process fake of the Amazon OpenSearch Service control plane. The data plane reuses the parlel elasticsearch emulator.

PropertyValue
Port4726
ProtocolREST/JSON (paths under /2021-01-01/opensearch)
HealthcheckGET /_parlel/health
ResetPOST /_parlel/reset

Default connection

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

Supported operations / paths

OperationPath
CreateDomainPOST /2021-01-01/opensearch/domain
DescribeDomainGET /2021-01-01/opensearch/domain/{name}
ListDomainNamesGET /2021-01-01/opensearch/domain
DescribeDomainsPOST /2021-01-01/opensearch/domain-info
DeleteDomainDELETE /2021-01-01/opensearch/domain/{name}

SDK example

import { OpenSearchClient, CreateDomainCommand } from "@aws-sdk/client-opensearch";

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

const { DomainStatus } = await os.send(new CreateDomainCommand({ DomainName: "logs" }));
console.log(DomainStatus?.Endpoint); // search-logs-parlel.us-east-1.es.amazonaws.com

For indexing/searching documents, point an OpenSearch/Elasticsearch client at the parlel elasticsearch emulator.

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
Data planeThis is control-plane only — use the elasticsearch emulator.
ProvisioningDomains are usable immediately; cluster config is cosmetic.
VPC / IAMNetwork and access policies are stored but not enforced.
UpgradesUpgradeDomain is not implemented.
<!-- 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:4726
<!-- parlel:testenv:end -->