v1.4.0

What's Changed

[1.4.0] "Areson" — 2026-07-08

Added

• Multi-region support — resource state is now isolated per account and region. The request region is taken from the SigV4 credential scope (Authorization header or presigned X-Amz-Credential query parameter), so two clients pointed at different regions see fully independent state, matching real AWS. Region-isolated in this release: AppConfig, Bedrock, Bedrock Agent, Bedrock Agent Runtime, Bedrock Runtime, CloudWatch, CloudWatch Logs, DynamoDB (tables, metadata, and Streams), Lambda (functions, event source mappings, durable executions), MSK, RDS, S3 Tables, Secrets Manager, SQS, SSM Parameter Store, and Step Functions. Cross-resource references resolve in the referenced ARN's own account and region (SNS→SQS fanout, EventBridge targets, ESM sources), background workers (event source pollers, the EventBridge scheduler tick, durable-function resume) re-scope to each resource's tenant, and ARNs are parsed and validated everywhere — cross-region references that real AWS rejects now return the same errors AWS returns. Persisted state moves to an on-disk format v2 with a version stamp (a newer-format file is refused instead of mis-parsed on downgrade); legacy account-scoped state files load and migrate automatically, recovering each record's region from its stored ARNs. Services not listed above keep sharing state across regions within an account, exactly as in 1.3.x — region isolation for them lands in subsequent releases. Note for PERSIST_STATE users: legacy records that carry no ARN migrate to the default region (MINISTACK_REGION), so pre-1.4 state created with a client region different from MINISTACK_REGION in a non-ARN service reads back under the default region. Contributed by @Areson.
• Amazon Bedrock — four new services — the full local Bedrock surface: bedrock control plane (66 operations verified against botocore — foundation-model catalog with real model IDs, inference profiles, guardrails with versioning, custom and imported models, provisioned throughput, and the customization / import / copy / batch-invocation job families), bedrock-runtime (Converse, ConverseStream, InvokeModel, InvokeModelWithResponseStream with real eventstream wire format, ApplyGuardrail, and async invokes — deterministic family-aware mock responses selected by model ID prefix for Anthropic, Titan, Nova, Llama, Mistral, Cohere, and AI21 shapes), bedrock-agent (72 operations — agents, knowledge bases, data sources, ingestion jobs, flows, prompts, tags), and bedrock-agent-runtime (31 operations — InvokeAgent, Retrieve/RetrieveAndGenerate, reranking, sessions, flow executions, prompt optimization). Led by @dcabib.
• Amazon MSK — Kafka control plane: cluster lifecycle (CreateCluster, ListClusters, DescribeCluster, DeleteCluster, ListNodes), configurations with revisions, SCRAM secret association, and tagging. GetBootstrapBrokers honors MINISTACK_MSK_BOOTSTRAP so clients route to a real broker you bring (Redpanda, Kafka, KRaft) while the control plane stays emulated; the Kafka wire protocol itself is not emulated.