Skip to content

Ministack: Free, open-source local AWS emulator - 60+ services, Terraform compatible, real databases. Free forever. MIT licensed.

release v1.5.17 (#1824)

Nahuel Nucera5ca080a1e0aa
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 83fb8cec..07fde2da 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -5,35 +5,25 @@ All notable changes to MiniStack will be documented here.
Format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
Versioning follows [Semantic Versioning](https://semver.org/).
-## [Unreleased]
-
-### Added
-
-- **CloudFront — public keys and key groups** — `CreatePublicKey`, `GetPublicKey`, `GetPublicKeyConfig`, `UpdatePublicKey`, `DeletePublicKey`, `ListPublicKeys`, `CreateKeyGroup`, `GetKeyGroup`, `GetKeyGroupConfig`, `UpdateKeyGroup`, `DeleteKeyGroup`, `ListKeyGroups`, so `aws_cloudfront_public_key` / `aws_cloudfront_key_group` (and Upbound's Terraform-based `provider-aws-cloudfront`) apply instead of hitting `NoSuchResource` on every create. Key groups validate their `Items` against real public keys, `DeletePublicKey` refuses a key still referenced by a key group, and `DeleteKeyGroup` refuses a group still referenced by a distribution's trusted key groups — both ETag/`If-Match` optimistic concurrency like the other CloudFront policy families. Contributed by @fabio-andre-rodrigues.
-- **Step Functions — execution history pagination** — `GetExecutionHistory` accepts `nextToken` and returns successive pages in forward or reverse order, with a token only while more events remain. `includeExecutionData=false` omits input and output payloads from returned history events.
-- **CloudFront — public keys and key groups** — `CreatePublicKey`, `GetPublicKey`, `GetPublicKeyConfig`, `UpdatePublicKey`, `DeletePublicKey`, `ListPublicKeys`, `CreateKeyGroup`, `GetKeyGroup`, `GetKeyGroupConfig`, `UpdateKeyGroup`, `DeleteKeyGroup`, `ListKeyGroups`, so `aws_cloudfront_public_key` / `aws_cloudfront_key_group` (and Upbound's Terraform-based `provider-aws-cloudfront`) apply instead of hitting `NoSuchResource` on every create. Key groups validate their `Items` against real public keys, `DeletePublicKey` refuses a key still referenced by a key group, and `DeleteKeyGroup` refuses a group still referenced by a distribution's trusted key groups — both ETag/`If-Match` optimistic concurrency like the other CloudFront policy families.
-- **CloudFormation — AppConfig applications, environments, configuration profiles and deployment strategies update in place** — none of the four had an update handler, so any property change re-ran the create and the resource came back under a new id. The environments, configuration profiles and hosted configuration versions keyed by the old id were orphaned. Each type now updates in place what its resource reference lists as No interruption and replaces on the rest. Contributed by @iot-rocket.
-- **CloudFormation — AppSync GraphQL APIs and API keys update in place** — every property of `AWS::AppSync::GraphQLApi` is No interruption, but a change re-ran the create, which minted a new api id with empty key, data source, resolver and type stores, so a renamed API came back empty. The API now keeps its id and applies the change in place. It stores `AdditionalAuthenticationProviders`, `XrayEnabled`, `QueryDepthLimit`, `ResolverCountLimit`, `IntrospectionConfig`, `EnvironmentVariables`, `OwnerContact`, `LogConfig`, `UserPoolConfig`, `OpenIDConnectConfig`, `LambdaAuthorizerConfig`, `EnhancedMetricsConfig` and `MergedApiExecutionRoleArn` in AppSync's camelCase, and a removed member goes back to AppSync's default. A `Visibility` change fails with AWS's message. The API carries the stack-level tags, its id has `CreateGraphqlApi`'s 26 characters (eight made an ARN botocore refuses) and it answers the `REALTIME` endpoint. `AWS::AppSync::ApiKey` keeps its key on a `Description` or `Expires` change, and its record carries `description` and `createdAt`, as `CreateApiKey` writes them. Contributed by @iot-rocket.
-- **CloudFormation — Auto Scaling groups, scaling policies and scheduled actions update in place** — a change re-ran the create, which mints a new ARN from a uuid, and the group also lost its instances and its creation time. The three types now update in place. An `AutoScalingGroupName` or `InstanceId` change replaces the group, and a group tag change keeps tags added through `CreateOrUpdateTags`. As on AWS, `PolicyName` names a scaling policy at create and is ignored after that, and CloudFormation names a scheduled action itself, ignores `ScheduledActionName` and answers the generated name through `Ref` (it answered the ARN). `DescribeAutoScalingGroups` answers the launch template's name beside its id. Contributed by @iot-rocket.
-- **CloudFormation — a VPC updates in place and is deleted with its default children** — `EnableDnsSupport`, `EnableDnsHostnames` and `Tags` are No interruption, but a change re-ran the create, which mints a new `vpc-` id. The delete removed only the VPC, so each change left its default security group, main route table and network ACL behind. The VPC now updates in place, and a removed DNS property goes back to its default. The delete goes through `DeleteVpc`, which removes the default children and fails with `DependencyViolation` while a security group created outside the stack is still in the VPC; AWS keeps that VPC too and retries the delete for a long time. The create applies the two DNS properties and the template's tags, which it ignored. `Ipv4IpamPoolId`, `Ipv4NetmaskLength` and `VpcEncryptionControl` replace the VPC, like `CidrBlock`. Contributed by @iot-rocket.
-- **CloudFormation — a subnet updates in place** — `MapPublicIpOnLaunch`, `PrivateDnsNameOptionsOnLaunch`, `EnableDns64` and `Tags` are No interruption, but a change re-ran the create, which mints a new `subnet-` id and left every instance, network interface and NAT gateway on an id that no longer resolves. They are applied in place now, and a property the template removes keeps its value, as on AWS. `EnableDns64` without an IPv6 block fails with AWS's message. `AvailabilityZoneId` is honoured, and it, the IPAM members, `Ipv6Native` and `OutpostArn` replace the subnet. A `MapPublicIpOnLaunch` of `"false"` reads false. Contributed by @iot-rocket.
-- **CloudFormation — a security group updates its rules in place** — `SecurityGroupIngress` and `SecurityGroupEgress` are updated in place on AWS and `Tags` is No interruption, but a change re-ran the create, which mints a new `sg-` id and lost every rule authorized outside the template. The rules are reconciled now: dropped ones are removed, new ones added, a changed `Description` is applied, and rules added outside the template stay. The create applies `SecurityGroupEgress`, which it ignored, and adds the allow-all egress rule only when the template declares none. An update that declares egress removes that rule, and one that drops the declaration leaves no egress rule, as on AWS. A rule's `Description`, `CidrIpv6`, prefix-list source or destination and a source group's name and owner are kept. Contributed by @iot-rocket.
-- **CloudFormation — a launch template change adds a version** — `LaunchTemplateData`, `TagSpecifications` and `VersionDescription` are No interruption, but a change re-ran the create, which minted a new `lt-` id and reset `LatestVersionNumber` and `DefaultVersionNumber` to 1. Each change now adds a version to the same template and the default version stays where it is, as measured on AWS. A rollback adds a version with the old data. The template's own tags come from its `TagSpecifications` entry for `launch-template` and are applied at create only (the create read a `Tags` property the type does not have). Contributed by @iot-rocket.
-- **CloudFormation — an internet gateway keeps its id and its attachment** — `Tags` is the only property of `AWS::EC2::InternetGateway` and it is No interruption, but the create ignored it, so a tag change minted a new `igw-` id, reset `Attachments` and applied no tags. The gateway now keeps its id and attachment and its tags are applied. Contributed by @iot-rocket.
-- **CloudFormation — a route table keeps its routes and associations** — `Tags` is No interruption on `AWS::EC2::RouteTable`, but a tag change re-ran the create, which minted a new `rtb-` id with only the local route and no associations, so everything added through `CreateRoute` or `AssociateRouteTable` was lost. The table now keeps its id, routes and associations, and its tags are applied. Contributed by @iot-rocket.
-- **CloudFormation — a route target change updates the route in place** — every target property of `AWS::EC2::Route` is No interruption, but the physical id `"{table}|{destination}"` did not move, so the create appended a second route for the same destination. The update and the create now replace the route for that destination, and the ten targets the create dropped are read, `OdbNetworkArn` included. The destination is read from `DestinationCidrBlock`, `DestinationIpv6CidrBlock` or `DestinationPrefixListId`: an IPv6 or prefix-list route overwrote the IPv4 default route, where AWS keeps them side by side. Contributed by @iot-rocket.
-
-### Fixed
-
-- **Lambda — `ReservedConcurrentExecutions=0` disables the function** — a zero reservation was treated as unset, so the function ran unbounded instead of throttling every invoke with `TooManyRequestsException`. Zero now throttles across all executors, the Docker pool, and SQS event source mappings. Contributed by @AdrianAcala.
-- **Step Functions — Secrets Manager binary values** — `aws-sdk:secretsmanager:getSecretValue`, `createSecret`, and `putSecretValue` now pass literal UTF-8 text in `SecretBinary`, matching the AWS SDK integration rather than exposing the HTTP API's base64 representation. Direct Secrets Manager API/SDK calls keep their existing binary encoding.
-- **Auto Scaling — scaling policies and scheduled actions keep their members** — `PutScalingPolicy` and `DescribePolicies` dropped `TargetTrackingConfiguration`, `StepAdjustments`, `PredictiveScalingConfiguration`, `EstimatedInstanceWarmup`, `MetricAggregationType` and `MinAdjustmentMagnitude`. They are stored and answered typed as on AWS, with only the members the policy type has, and `MaxCapacityBreachBehavior` defaults to `HonorMaxCapacity`. A member that is not a number gives `ValidationError` instead of a 500. `Alarms` stays empty where AWS lists the target tracking alarms. Scheduled actions keep `StartTime`, `EndTime` and `TimeZone`, and `DescribeScheduledActions` answers them with `Recurrence` and the sizes. Contributed by @iot-rocket.
-- **EC2 — subnets answer their DNS and IPv6 attributes** — `DescribeSubnets` answers `PrivateDnsNameOptionsOnLaunch`, `EnableDns64`, `Ipv6Native` and `AssignIpv6AddressOnCreation`, which it did not render, with AWS's defaults for a subnet created without them. `ModifySubnetAttribute` changes the private DNS name options. Contributed by @iot-rocket.
-- **EC2 — launch templates answer their tags and list versions newest first** — `CreateLaunchTemplate` and `DescribeLaunchTemplates` rendered tags under `tags`, so botocore dropped them; they answer `tagSet` now. `DescribeLaunchTemplateVersions` lists the newest version first, as AWS does. Contributed by @iot-rocket.
-- **EC2 — `DescribeRouteTables` answers every route destination and target** — an IPv6 or prefix-list route came back with an empty `destinationCidrBlock`, and only five target types were rendered. All destinations and targets are answered now, a VPC endpoint target as `gatewayId`. Contributed by @iot-rocket.
-- **CloudFormation — a failed update rolls back its in-place changes** — the rollback kept every resource that existed before the update but did not undo what the update had changed on it, the limitation 1.5.8 shipped with. Each changed resource now goes back through its type's update handler with `UPDATE_IN_PROGRESS` / `UPDATE_COMPLETE` events, before the cleanup deletes what the update created. A custom resource whose own update failed is sent back too, and a revert that fails lands the stack in `UPDATE_ROLLBACK_FAILED`, which `ContinueUpdateRollback` retries or skips. `UPDATE_ROLLBACK_IN_PROGRESS` names the failed resource, the cleanup runs in `UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS` with `DELETE_IN_PROGRESS` events, and a delete that fails there no longer fails the rollback. An executed change set that rolls back restores the stack's parameters. AWS reverts resources in parallel, the emulator one after the other. Contributed by @iot-rocket.
-- **CloudFormation — an ECS cluster reads its settings back** — `ClusterSettings`, `DefaultCapacityProviderStrategy` and `Configuration` of `AWS::ECS::Cluster` were stored in the template's PascalCase (`Configuration` not at all), so `DescribeClusters` answered `[{}]` for the settings and the strategy. All three are stored in the API's camelCase now. `DescribeClusters` answers them also without `include`, where AWS needs `SETTINGS` or `CONFIGURATIONS`. Contributed by @iot-rocket.
-- **CloudFormation — VPCs, subnets, security groups, internet gateways and route tables carry the stack's tags** — the five types carried only the template's own tags. They now also get the stack-level tags and the three `aws:cloudformation:` tags, as on AWS, and a stack tag change is applied to them in place. Contributed by @iot-rocket.
+## [1.5.17] — 2026-09-25
+
+### Added
+
+- **Lambda MicroVMs — images build and run in Docker** — with Docker available, `CreateMicrovmImage` / `UpdateMicrovmImage` build the `codeArtifact` Dockerfile (`CREATING` → `CREATED` / `CREATE_FAILED`), call the `/ready` and `/validate` hooks, and `RunMicrovm` runs the image. Only the disk is snapshotted. Contributed by @edersonbrilhante.
+- **CloudFront — public keys and key groups** — `CreatePublicKey`, `GetPublicKey`, `GetPublicKeyConfig`, `UpdatePublicKey`, `DeletePublicKey`, `ListPublicKeys` and the same six for key groups, with `PublicKeyInUse` / `ResourceInUse` on delete. Contributed by @fabio-andre-rodrigues.
+- **Step Functions — execution history pagination** — `GetExecutionHistory` pages with `nextToken`, and `includeExecutionData=false` drops input and output. Contributed by @jayjanssen.
+- **CloudFormation — more types update in place** — AppConfig, AppSync GraphQL APIs and API keys, Auto Scaling groups, policies and scheduled actions, VPCs, subnets, security groups, launch templates, internet gateways, route tables and routes keep their id on a No interruption change instead of being recreated. Contributed by @iot-rocket.
+
+### Fixed
+
+- **CloudFormation — import change sets are validated and refused** — `IMPORT` change sets are validated and listed as `Import` changes; executing one is refused. Every change carries `Type: Resource`. Contributed by @iot-rocket.
+- **SSM — `GetParameter` reads `name:version` and `name:label`** — they answered `ParameterNotFound`; a missing version or label is `ParameterVersionNotFound`. Reported by @lobodpav.
+- **Lambda — `ReservedConcurrentExecutions=0` throttles every invoke** — zero was treated as unset. Contributed by @AdrianAcala.
+- **Step Functions — Secrets Manager `SecretBinary`** — the SDK integration passes literal text instead of base64. Contributed by @jayjanssen.
+- **Auto Scaling — scaling policies and scheduled actions keep their members** — target tracking, step and predictive settings, `StartTime`, `EndTime` and `TimeZone` were dropped. Contributed by @iot-rocket.
+- **EC2 — subnets, launch templates and route tables answer their attributes** — subnet DNS and IPv6 attributes, launch template `tagSet` and newest-first versions, and every route destination and target. Contributed by @iot-rocket.
+- **CloudFormation — a failed update rolls back its in-place changes** — changed resources are reverted, and a failed revert lands in `UPDATE_ROLLBACK_FAILED`. Contributed by @iot-rocket.
+- **CloudFormation — ECS cluster settings and stack tags** — `ClusterSettings`, `DefaultCapacityProviderStrategy` and `Configuration` read back, and EC2 network resources carry the stack's tags. Contributed by @iot-rocket.
## [1.5.16] — 2026-09-23
diff --git a/README.md b/README.md
index fd753eb9..012cca0a 100644
--- a/README.md
+++ b/README.md
@@ -420,7 +420,7 @@ subnet = ec2.create_subnet(
| Service | Operations | Notes |
|---------|-----------|-------|
-| **SSM Parameter Store** | PutParameter, GetParameter, GetParameters, GetParametersByPath, DeleteParameter, DeleteParameters, DescribeParameters, GetParameterHistory, LabelParameterVersion, AddTagsToResource, RemoveTagsFromResource, ListTagsForResource | Supports String, SecureString, StringList |
+| **SSM Parameter Store** | PutParameter, GetParameter, GetParameters, GetParametersByPath, DeleteParameter, DeleteParameters, DescribeParameters, GetParameterHistory, LabelParameterVersion, AddTagsToResource, RemoveTagsFromResource, ListTagsForResource | Supports String, SecureString, StringList; `name:version` and `name:label` selectors on `GetParameter` / `GetParameters` |
| **EventBridge** | CreateEventBus, UpdateEventBus, DeleteEventBus, ListEventBuses, DescribeEventBus, PutRule, DeleteRule, ListRules, DescribeRule, EnableRule, DisableRule, PutTargets, RemoveTargets, ListTargetsByRule, ListRuleNamesByTarget, PutEvents, TestEventPattern, TagResource, UntagResource, ListTagsForResource, CreateArchive, DeleteArchive, DescribeArchive, UpdateArchive, ListArchives, PutPermission, RemovePermission, CreateConnection, DescribeConnection, DeleteConnection, UpdateConnection, DeauthorizeConnection, ListConnections, CreateApiDestination, DescribeApiDestination, DeleteApiDestination, UpdateApiDestination, ListApiDestinations, StartReplay, DescribeReplay, ListReplays, CancelReplay, CreateEndpoint, DeleteEndpoint, DescribeEndpoint, ListEndpoints, UpdateEndpoint, ActivateEventSource, DeactivateEventSource, DescribeEventSource, CreatePartnerEventSource, DeletePartnerEventSource, DescribePartnerEventSource, ListPartnerEventSources, ListPartnerEventSourceAccounts, ListEventSources, PutPartnerEvents | Lambda target dispatch on PutEvents; S3 EventBridge notifications; archives capture matching events and `StartReplay` re-dispatches them to the destination bus in a background thread; API destination targets are **invoked over HTTP** on PutEvents — connection auth (Basic, API Key, OAuth client-credentials with token caching and 401/407 refresh), connection/target header/query/body parameter merging with connection precedence, `*` path parameters, dynamic JSON-path parameter values resolved from the untransformed event, and the AWS default headers (`User-Agent: Amazon/EventBridge/ApiDestinations`, default `Content-Type: application/json; charset=utf-8`), which connection and target parameters cannot override; redirects are not followed (a `3xx` is a non-retryable delivery failure), only `http(s)` invocation and OAuth authorization endpoints are accepted, `HttpMethod` and `AuthorizationType` are validated against their enums, and a connection that is not `AUTHORIZED` is not invoked (`DeauthorizeConnection` clears its stored credentials) — the 24h retry pipeline, rate limiting, and DLQs are not modeled; SaaS/partner APIs are otherwise control-plane stubs. Event patterns are **validated** — `PutRule`, `TestEventPattern`, `CreateArchive` and `UpdateArchive` reject a malformed pattern with `InvalidEventPatternException` carrying AWS's own reason text — and evaluate `prefix`/`suffix` (plain or case-insensitive via a nested `equals-ignore-case`), `wildcard` (AWS semantics — only `*` is special, `\` escapes — with catastrophic backtracking ruled out), `equals-ignore-case` (AWS's per-character case alternation), `exactly`, `cidr` (IPv4/IPv6, host bits floored, `/32` and `/128` refused as AWS refuses them), `numeric` (as the grammar it is: one comparison or a lower-then-upper bound), `exists` (leaf nodes only, so an object or an empty array does not exist), `anything-but` (a literal, a list, or a nested `prefix`/`suffix`/`wildcard`/`equals-ignore-case`, singly or as a list), and `$or` at any field position — expanded into flat alternatives at rule creation, so AWS's per-leaf last-write-wins collision rule and its 1000-combination cap both hold. All ten envelope fields are filterable, an unmodelled key is a path the event lacks rather than an error, `resources` is an intersection, array values are matched per element (with AWS's array-consistency rule), and values compare as JSON so a string never equals a number. An operand or key the matcher cannot evaluate never matches, rather than raising or matching everything. Not modeled: the 4096-character pattern limit, the wildcard-complexity refusal, and the 256-leaf rule-size cap |
| **Kinesis** | CreateStream, DeleteStream, DescribeStream, DescribeStreamSummary, ListStreams, ListShards, PutRecord, PutRecords, GetShardIterator, GetRecords, IncreaseStreamRetentionPeriod, DecreaseStreamRetentionPeriod, MergeShards, SplitShard, UpdateShardCount, StartStreamEncryption, StopStreamEncryption, EnableEnhancedMonitoring, DisableEnhancedMonitoring, RegisterStreamConsumer, DeregisterStreamConsumer, ListStreamConsumers, DescribeStreamConsumer, AddTagsToStream, RemoveTagsFromStream, ListTagsForStream | Partition key → shard routing; AWS limits enforced (1 MB/record, 500 records/batch, 5 MB payload, 256-char partition key) |
| **CloudWatch Metrics** | PutMetricData, GetMetricStatistics, GetMetricData, ListMetrics, PutMetricAlarm, PutCompositeAlarm, DescribeAlarms, DescribeAlarmsForMetric, DescribeAlarmHistory, DeleteAlarms, SetAlarmState, EnableAlarmActions, DisableAlarmActions, TagResource, UntagResource, ListTagsForResource, PutDashboard, GetDashboard, DeleteDashboards, ListDashboards | CBOR and JSON protocol |
diff --git a/pyproject.toml b/pyproject.toml
index 884a7484..b6181e69 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
[project]
name = "ministack"
-version = "1.5.16"
+version = "1.5.17"
description = "Free, open-source local AWS emulator — drop-in LocalStack replacement"
readme = "README.md"
license = { file = "LICENSE" }