appconfig (parlel)

A zero-dependency, in-process fake of AWS AppConfig. Speaks the AppConfig REST/JSON API.

FieldValue
Serviceappconfig
Port4739
ProtocolREST / JSON
HealthGET /_parlel/health
ResetPOST /_parlel/reset

Default connection

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

Supported operations

OperationHTTP
CreateApplicationPOST /applications
ListApplicationsGET /applications
GetApplicationGET /applications/{id}
CreateEnvironmentPOST /applications/{id}/environments
ListEnvironmentsGET /applications/{id}/environments
CreateConfigurationProfilePOST /applications/{id}/configurationprofiles
ListConfigurationProfilesGET /applications/{id}/configurationprofiles
StartDeploymentPOST /applications/{id}/environments/{envId}/deployments
(helper) ListDeploymentsGET /applications/{id}/environments/{envId}/deployments

Deployments complete synchronously (State: COMPLETE, 100%).

SDK example

import { AppConfigClient, CreateApplicationCommand } from "@aws-sdk/client-appconfig";

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

const app = await ac.send(new CreateApplicationCommand({ Name: "my-app" }));

Access via MCP / preview URL

Under the parlel pool, reach this service through the MCP gateway and the pool's preview 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
Deployment strategiesStrategy IDs accepted but not enforced (no bake/rollout time).
Configuration dataGetConfiguration/GetLatestConfiguration not implemented.
ValidatorsStored but never executed.
PaginationItems returned in full, no NextToken.
<!-- 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:4739
<!-- parlel:testenv:end -->