cloud-map — AWS Cloud Map (Service Discovery)

A zero-dependency, in-process emulator for AWS Cloud Map (Route 53 Auto Naming): namespaces, services, and instances with service discovery.

PropertyValue
Port4717
ProtocolAWS JSON 1.1
Target prefixRoute53AutoNaming_v20170314
HealthGET /_parlel/health
ResetPOST /_parlel/reset

Default connection

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

Supported operations

OperationNotes
CreateHttpNamespaceReturns OperationId
CreatePrivateDnsNamespaceReturns OperationId
CreatePublicDnsNamespaceReturns OperationId
ListNamespaces
GetNamespace
DeleteNamespaceFails if it still contains services
CreateService
ListServicesFilter by NAMESPACE_ID
GetService
DeleteServiceFails if it still contains instances
RegisterInstanceReturns OperationId
DeregisterInstanceReturns OperationId
GetInstance
ListInstances
DiscoverInstancesFiltered by QueryParameters
GetOperationAlways SUCCESS

SDK usage example

import {
  ServiceDiscoveryClient,
  CreateHttpNamespaceCommand,
  DiscoverInstancesCommand,
} from "@aws-sdk/client-servicediscovery";

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

await sd.send(new CreateHttpNamespaceCommand({ Name: "my-ns" }));

Access via MCP / preview URL

Point any AWS SDK or MCP tool at the allocated preview URL via AWS_ENDPOINT_URL.

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
DNS resolutionNo actual DNS records are created or resolved
Health checksInstances are always reported HEALTHY
OperationsAll operations complete instantly with SUCCESS
Update operationsUpdate operations are not implemented
StateIn-memory only; lost on restart
<!-- 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:4717
<!-- parlel:testenv:end -->