Skip to content

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

release v1.5.31 (#2368)

Nahuel Nucerab833c07a818a
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 1720ce65..8ae1860e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,36 +7,29 @@ Versioning follows [Semantic Versioning](https://semver.org/).
## [Unreleased]
-### Added
-- **CloudFront — web ACL association for distributions** — `AssociateDistributionWebACL` and `DisassociateDistributionWebACL` set and clear `WebACLId` in the distribution's config, so `GetDistribution`, `GetDistributionConfig` and `ListDistributions` report it, and answer with the new `ETag`. They need the current `If-Match` (`InvalidIfMatchVersion`, `PreconditionFailed`) and a `WebACLArn`, and a missing distribution answers `EntityNotFound`; `AssociateDistributionWebACL` returns the `WebACLArn`. The web ACL is not looked up and is not evaluated. Contributed by @OS-kiranmalsetty.
-- **Cognito — auth events** — `AdminListUserAuthEvents` always answered an empty list; on a pool with threat protection on (`AdvancedSecurityMode` `AUDIT` or `ENFORCED`), password, SRP and admin sign-ins, their MFA answers and password changes are now logged as `SignIn` and `PasswordChange` events with the caller's address, listed newest first with `MaxResults`/`NextToken` paging, and `AdminUpdateAuthEventFeedback` and `UpdateAuthEventFeedback` are implemented. Contributed by @iot-rocket.
-- **Route 53 — VPC associations for private hosted zones** — `AssociateVPCWithHostedZone`, `DisassociateVPCFromHostedZone` and `ListHostedZonesByVPC` (paged with `MaxItems` and `NextToken`). They refuse a public zone (`PublicZoneVPCAssociation`), a VPC already associated with a zone of the same name (`ConflictingDomainExists`), a VPC the zone doesn't have (404 `VPCAssociationNotFound`) and the zone's last VPC (`LastVPCAssociation`). Contributed by @kharabasz.
-- **CloudFront — VPC origins** — `CreateVpcOrigin`, `GetVpcOrigin`, `UpdateVpcOrigin`, `DeleteVpcOrigin` and `ListVpcOrigins` replace the empty `ListVpcOrigins` stub, so Terraform's `aws_cloudfront_vpc_origin` and a distribution's `vpc_origin_config` apply. As on AWS, a create, update or delete answers `Deploying`; MiniStack then finishes it at once, so the next read shows `Deployed` with the next `ETag`, or 404 after a delete. Names are unique per account, endpoints are not, and an origin a distribution names can't be deleted or changed. Validation, its order, the `TLSv1`/`TLSv1.1`/`TLSv1.2` default, `IpAddressType`, the list paging (no `Marker` or `IsTruncated`) and the IAM resources follow AWS captures. The endpoint has to be a load balancer or instance that exists in MiniStack, and viewer requests are not routed to it. Contributed by @kharabasz.
-
-### Fixed
-- **Auth — requests through an S3 access point are checked on the access point and its bucket** — under `AUTH=true` a request through an access point alias was checked on `arn:aws:s3:::<alias>`, so a policy naming the bucket or the access point refused it, and a request through the access point ARN was checked on the bucket only; both are now checked on the access point and on its bucket, each with `s3:DataAccessPointArn`, `s3:DataAccessPointAccount` and `s3:AccessPointNetworkOrigin`, and the bucket policy applies. Contributed by @iot-rocket.
-- **S3 Control — Multi-Region Access Point requests authorize the operation they run** — the action was read from the end of the path, so an MRAP named `policy` was authorized as its policy and a trailing slash after `/policy` or `/routes` was authorized for that operation and served as `GetMultiRegionAccessPoint`; the action now comes from the route the handler serves, a method a resource lacks answers 405 `MethodNotAllowed` with `Method` and `ResourceType`, and a path S3 Control cannot parse 400 `InvalidURI`. Contributed by @iot-rocket.
-- **S3 Control — access point requests authorize the operation they run** — access point and Object Lambda Access Point requests were authorized by a second reading of the path, so a POST on a policy returned it, an extra segment or a double slash deleted the Object Lambda Access Point or set its policy without the action, and an access point named `policy` was authorized as its policy; the action now comes from the route the handler serves, a method a resource lacks answers 405 `MethodNotAllowed` with `Method` and `ResourceType`, and a path S3 Control cannot parse 400 `InvalidURI`. Contributed by @iot-rocket.
-- **Lambda — the local Node executor's SDK stubs sign their calls** — the `@aws-sdk/client-lambda` stub and the JSON-RPC `@aws-sdk/client-*` stubs sent their requests without credentials, so a call landed in the default account whatever account the function belongs to, and under `AUTH=true` it ran as the account root. They now sign with the function's credentials, as the real SDK does: with `AUTH` unset a call lands in the function's own account, under `AUTH=true` it runs as the execution role. Contributed by @iot-rocket.
-- **IoT — `#` does not match the level above it** — a subscription or topic rule with a filter ending in `/#` (`a/c2/#`) also got messages published to the level above (`a/c2`), as the MQTT specification allows; AWS IoT Core delivers only `a/c2/` and deeper, and so does the broker now, for subscriptions and rules. A republish topic at that level is still refused, as on AWS. Contributed by @iot-rocket.
-- **EventBridge — archive KMS keys** — `CreateArchive` and `UpdateArchive` dropped `KmsKeyIdentifier`, so `DescribeArchive` never returned it and Terraform re-planned `kms_key_identifier` on every run; the key is now stored and returned, an update that omits it keeps it, and an empty identifier on update clears it; `ListArchives` entries carry only the `Archive` summary fields. Contributed by @kharabasz.
-- **WAF v2 — `CreateIPSet` and `CreateRuleGroup` refuse a duplicate name** — a second IP set or rule group with the name and scope of an existing one is now refused with `WAFDuplicateItemException` (`AWS WAF couldn’t perform the operation because some resource in your request is a duplicate of an existing one.`, also from `CreateWebACL` and `CreateRegexPatternSet`). Both stored the duplicate silently, so a client that retries a create after losing the response ended up with two. Contributed by @OS-kiranmalsetty.
-- **Cognito — pre token generation event fields** — the event always said `"version": "1"`, a `NEW_PASSWORD_REQUIRED` answer was `TokenGeneration_Authentication` and a `client_credentials` grant had an empty `userName`; the event now carries `"1"`, `"2"` or `"3"` for `V1_0`, `V2_0` and `V3_0`, `TokenGeneration_NewPasswordChallenge` and `ClientCredentials`, as AWS sends them. Contributed by @iot-rocket.
-- **Cognito — unknown users** — calls for a user who does not exist answered `User <name> does not exist.`; they now answer `User does not exist.` as AWS does, and with `PreventUserExistenceErrors` `LEGACY` `ForgotPassword`, `ConfirmForgotPassword`, `ResendConfirmationCode` and `ConfirmSignUp` answer `Username/client id combination not found.`. With `ENABLED`, `ConfirmSignUp` answers `CodeMismatchException` instead of revealing that the user does not exist. Contributed by @iot-rocket.
-- **CloudFormation — S3 bucket CORS, Block Public Access and website** — `AWS::S3::Bucket` applied only `VersioningConfiguration` and `NotificationConfiguration` and dropped `CorsConfiguration`, `PublicAccessBlockConfiguration` and `WebsiteConfiguration`, so `GetBucketCors`, `GetPublicAccessBlock` and `GetBucketWebsite` found no configuration after a stack create; the three are now stored on create, replaced on update and deleted when an update removes them. Contributed by @iot-rocket.
-- **S3 — access point Block Public Access** — requests through an access point alias or ARN followed the bucket's Block Public Access settings alone, so a public ACL sent through an access point with the default settings was accepted. An access point's settings other than `BlockPublicPolicy` now count as the bucket's for requests through it, and its `BlockPublicAcls` refuses a public canned ACL, grant header or ACL body with 403 `AccessDenied`. Contributed by @iot-rocket.
-- **Lambda — Node.js HTTPS to a TLS gateway in the local executor** — with `USE_SSL=1` a Node function's `https` requests to the gateway went out as plain HTTP to its TLS port and the built-in SDK v3 clients always spoke HTTP, so custom resource callbacks and SDK calls failed with `socket hang up`; they now keep TLS on the gateway port, and `https.request` or `https.get` with a URL plus options no longer throws `ERR_INVALID_ARG_TYPE`. Contributed by @iot-rocket.
-- **Lambda — Node.js custom resource callbacks in the Docker executor under `USE_SSL`** — the Node shim kept the port of an https request to the gateway when `USE_SSL=1`, so a `cfn-response` or CDK style `ResponseURL` PUT (no port, or 443) went to port 443 and the stack waited out `ServiceTimeout`; it now goes to the gateway port over TLS, and other explicit ports are kept. Contributed by @iot-rocket.
-- **TLS — the generated certificate names `host.docker.internal`** — with `USE_SSL=1` and the Docker Lambda executor, functions reach the gateway as `https://host.docker.internal:<port>`, a name the generated certificate lacked, so every SDK call and callback from a container failed hostname verification; the certificate now carries it, and a cached one without it is regenerated. Contributed by @iot-rocket.
-- **SQS — FIFO dedup hit returns the current request's MD5s** — a `SendMessage` (or `SendMessageBatch` entry) whose `MessageDeduplicationId` was already in the 5-minute window answered with the first message's `MD5OfMessageBody` and `MD5OfMessageAttributes`; AWS keeps the first message but reports the digests of the request just sent, and SDKs that verify them (.NET, Java) threw `MD5 hash mismatch` on every replay whose body or attributes differed. The response now carries the current request's digests; `MessageId` and `SequenceNumber` are still the first message's. Contributed by @vanessah07.
-- **S3 — `EU` location constraint** — since 1.5.28, `CreateBucket` from an eu-west-1 endpoint refused the legacy `EU` constraint with `IllegalLocationConstraintException`, and a bucket created with it elsewhere was homed in a region called `EU`. As on AWS, eu-west-1 now accepts `EU` and homes the bucket in eu-west-1, `GetBucketLocation` answers `EU` for it, and other regional endpoints still refuse it. The AWS SDK for .NET sends `EU` for eu-west-1 by default.
-- **Route 53 — private hosted zones keep their VPC** — `CreateHostedZone` with a `VPC` made a public zone and dropped the VPC, so Terraform's `aws_route53_zone` with a `vpc` block planned to add it again on every run; the zone is now private, the response carries the `VPC` instead of a delegation set, also on a `CallerReference` replay, and `GetHostedZone` returns its `VPCs`. Contributed by @kharabasz.
-- **ELBv2 — listener `SslPolicy` and certificate** — `CreateListener` and `ModifyListener` dropped `SslPolicy` and `Certificates`, so `DescribeListeners` returned neither and Terraform re-planned `ssl_policy` on every HTTPS listener; HTTPS and TLS listeners now keep and return both, the policy defaults to `ELBSecurityPolicy-2016-08`, a listener moved to HTTP or TCP drops them, and more than one default certificate answers `ValidationError`. Contributed by @kharabasz.
-- **ELBv2 — listener rule transforms** — `CreateRule` and `ModifyRule` dropped `Transforms`, so Terraform re-planned every `aws_lb_listener_rule` with a `transform` block; `url-rewrite` and `host-header-rewrite` transforms are now stored and returned by `DescribeRules` (an empty list for a rule without any), replaced by `ModifyRule` and cleared by `ResetTransforms`, and `AWS::ElasticLoadBalancingV2::ListenerRule` creates, updates and removes them. Invalid transforms are refused with AWS's messages and check order, as captured against AWS: the request-model errors first, then a missing load balancer, one transform per type, the type's config, one rewrite, the `Replace` and `Regex` lengths and characters, and the `Regex` syntax, all before a missing listener or rule. `ModifyRule` refuses `Transforms` with `ResetTransforms`, a call with nothing to change, and any change to a default rule (`OperationNotPermitted`). CloudFormation checks `Transforms` against the resource schema before provisioning and reports the handler's reason for the rest. The data plane does not apply transforms: requests reach targets with their original path, query string and Host header. Contributed by @kharabasz.
-- **S3 — replication rule options are kept and checked** — `PutBucketReplication` dropped `SourceSelectionCriteria` from each rule and `EncryptionConfiguration`, `ReplicationTime` and `Metrics` from its destination, so Terraform's `aws_s3_bucket_replication_configuration` planned a change on every run; `GetBucketReplication` now returns them as put, with `Minutes` as an integer. A put AWS refuses is refused with AWS's code, message and `ArgumentName`, in AWS's order, and stores nothing: `MalformedXML` for a missing `Status`, `Time` or `Minutes`, an unknown or repeated element or a `Minutes` that is not a 32-bit integer, `InvalidArgument` for `Minutes` other than 15, a `ReplicaKmsKeyID` that is empty or not a KMS key or alias ARN, and an event threshold that doesn't fit the `ReplicationTime` status, and `InvalidRequest` for `ReplicationTime` without `Metrics`, `SseKmsEncryptedObjects` and `EncryptionConfiguration` without each other, an `EncryptionConfiguration` without `ReplicaKmsKeyID`, an empty `SourceSelectionCriteria`, a key in another partition or region than the destination bucket, and `ReplicationTime`, `Metrics` or `ReplicaModifications` in a rule that uses `Prefix` instead of `Filter`. The options are stored only; they don't change which objects are replicated. Contributed by @kharabasz.
-- **Step Functions — `encryptionConfiguration` on state machines** — `CreateStateMachine` and `UpdateStateMachine` dropped `encryptionConfiguration`, so Terraform's `aws_sfn_state_machine` showed a diff on `encryption_configuration` after every apply. It is now stored and returned by `DescribeStateMachine`, published versions and `DescribeStateMachineForExecution`: `{"type": "AWS_OWNED_KEY"}` when none was set, and a customer managed key with `kmsDataKeyReusePeriodSeconds` 300 when no period was sent, on create and update. Requests are refused as AWS refuses them: `SerializationException` for wrong JSON types, `ValidationException` for the member constraints (several in one message), `InvalidEncryptionConfiguration` for a customer managed key without `kmsKeyId` or an `AWS_OWNED_KEY` with a key or period, and `MissingRequiredParameter` for an update without `definition`, in AWS's check order. A re-create with a different configuration answers `StateMachineAlreadyExists`. `AWS::StepFunctions::StateMachine` applies `EncryptionConfiguration` on create and update, keeps it when an update drops the block, and fails with AWS's handler messages. The key is not looked up in KMS. Contributed by @kharabasz.
-- **Cognito — `ChangePassword` checks `PreviousPassword`** — a wrong or missing `PreviousPassword` was ignored and the password was replaced; for a user with a password, a wrong one now fails with `NotAuthorizedException` and a missing one with `InvalidParameterException`, as on AWS, and the password is unchanged. Contributed by @jun-ut.
-- **SQS — `MD5OfMessageAttributes` of filtered attributes** — `ReceiveMessage` with `MessageAttributeNames` selecting some of a message's attributes returned only those attributes but the digest of all of them, so SDKs that validate `MD5OfMessageAttributes` rejected the response; the digest is now computed over the attributes returned. Contributed by @Xevos117.
+## [1.5.31] — 2026-10-21
+
+### Added
+- **CloudFront — VPC origins and distribution web ACLs** — `CreateVpcOrigin`, `GetVpcOrigin`, `UpdateVpcOrigin`, `DeleteVpcOrigin` and `ListVpcOrigins` are implemented: a change answers `Deploying` and the next read shows `Deployed`, the endpoint must be a load balancer or instance that exists in MiniStack, and an origin a distribution names can't be deleted or changed (`CannotDeleteEntityWhileInUse`, `CannotUpdateEntityWhileInUse`). `AssociateDistributionWebACL` and `DisassociateDistributionWebACL` set and clear the distribution's `WebACLId`, with `If-Match` and `EntityNotFound` as on AWS. Contributed by @kharabasz and @OS-kiranmalsetty.
+- **Cognito — auth events** — on a pool with threat protection on, password, SRP and admin sign-ins, their MFA answers and password changes are logged as `SignIn` and `PasswordChange` events, `AdminListUserAuthEvents` lists them newest first, and `AdminUpdateAuthEventFeedback` and `UpdateAuthEventFeedback` are implemented. Contributed by @iot-rocket.
+- **Route 53 — private hosted zones** — `CreateHostedZone` with a `VPC` made a public zone and dropped the VPC; the zone is now private and keeps its VPCs, and `AssociateVPCWithHostedZone`, `DisassociateVPCFromHostedZone` and `ListHostedZonesByVPC` are implemented with AWS's refusals (`PublicZoneVPCAssociation`, `ConflictingDomainExists`, `VPCAssociationNotFound`, `LastVPCAssociation`). A Cloud Map private DNS namespace's zone carries the namespace VPC. Contributed by @kharabasz.
+
+### Fixed
+- **S3 — access points** — under `AUTH=true` a request through an access point alias or ARN is now checked on both the access point and its bucket, with `s3:DataAccessPointArn`, `s3:DataAccessPointAccount` and `s3:AccessPointNetworkOrigin`, and the access point's Block Public Access settings apply to requests through it (`BlockPublicAcls` refuses a public ACL with 403 `AccessDenied`). Contributed by @iot-rocket.
+- **S3 Control — access point, Object Lambda and Multi-Region Access Point requests authorize the operation they run** — the IAM action was read from the path separately from the handler, so an extra segment, a double slash or a resource named `policy` ran an operation without its action; the action now comes from the route served, a method a resource lacks answers 405 `MethodNotAllowed` and an unparseable path 400 `InvalidURI`. Contributed by @iot-rocket.
+- **S3 — replication rule options** — `PutBucketReplication` dropped `SourceSelectionCriteria`, `EncryptionConfiguration`, `ReplicationTime` and `Metrics`; they are now stored, returned and validated with AWS's codes and order (`MalformedXML`, `InvalidArgument`, `InvalidRequest`). Contributed by @kharabasz.
+- **S3 — `EU` location constraint** — eu-west-1 accepts the legacy `EU` constraint again and homes the bucket in eu-west-1, `GetBucketLocation` answers `EU` for it, and other regional endpoints still refuse it. Contributed by @toby6578.
+- **CloudFormation — S3 bucket CORS, Block Public Access and website** — `AWS::S3::Bucket` dropped `CorsConfiguration`, `PublicAccessBlockConfiguration` and `WebsiteConfiguration`; they are now stored on create, replaced on update and deleted when an update removes them. Contributed by @iot-rocket.
+- **Lambda — Node.js functions** — under `USE_SSL=1` Node requests to the gateway keep TLS on the gateway port in both executors, so `cfn-response` callbacks and SDK calls work, and the generated certificate names `host.docker.internal`. The local executor's SDK stubs now sign with the function's credentials, so a call lands in the function's account and runs as its execution role. Contributed by @iot-rocket.
+- **ELBv2 — listener TLS settings and rule transforms** — HTTPS and TLS listeners keep `SslPolicy` (default `ELBSecurityPolicy-2016-08`) and their certificate, and more than one certificate answers `TooManyCertificates` (`Up to '1' certificate ARNs can be specified, but '2' were specified`). Rules keep their `url-rewrite` and `host-header-rewrite` `Transforms`, validated as AWS does, also from `AWS::ElasticLoadBalancingV2::ListenerRule`. Contributed by @kharabasz.
+- **Cognito — trigger events and user errors** — the pre token generation event carries its version, `TokenGeneration_NewPasswordChallenge` and `ClientCredentials`, and every trigger's `awsSdkVersion` is `aws-sdk-unknown-unknown`. Unknown users answer `User does not exist.` (`Username/client id combination not found.` on the client calls with `PreventUserExistenceErrors` `LEGACY`), and `ChangePassword` checks `PreviousPassword`. Contributed by @iot-rocket and @jun-ut.
+- **Step Functions — encryption and `aws-sdk:ec2` snapshots** — state machines keep and validate `encryptionConfiguration` (`AWS_OWNED_KEY` when unset, a 300-second key reuse period by default), also in `AWS::StepFunctions::StateMachine`, and `aws-sdk:ec2` snapshot results name their lifecycle `State`. Contributed by @kharabasz and @bandle.
+- **SQS — message digests** — a FIFO dedup hit answers the current request's `MD5OfMessageBody` and `MD5OfMessageAttributes`, and `ReceiveMessage` computes `MD5OfMessageAttributes` over the attributes it returns, so SDKs that verify them no longer fail. Contributed by @vanessah07 and @Xevos117.
+- **EventBridge — archive KMS keys** — `CreateArchive` and `UpdateArchive` keep `KmsKeyIdentifier` and `DescribeArchive` returns it; `ListArchives` entries carry only the `Archive` summary fields. Contributed by @kharabasz.
+- **WAF v2 — duplicate names** — `CreateIPSet` and `CreateRuleGroup` refuse a name already used in the scope, and all four creates answer `WAFDuplicateItemException` with `AWS WAF couldn’t perform the operation because some resource in your request is a duplicate of an existing one.` Contributed by @OS-kiranmalsetty.
+- **IoT — `#` does not match the level above it** — a filter ending in `/#` no longer receives messages published to the level above it, as on AWS IoT Core. Contributed by @iot-rocket.
+- **SSM — public latest Amazon Linux AMI parameters** — `/aws/service/ami-amazon-linux-latest/al2023-ami-kernel-default-x86_64` and the Amazon Linux 2 parameter resolve, also as CloudFormation `AWS::SSM::Parameter::Value<AWS::EC2::Image::Id>` defaults. Contributed by @bandle.
+- **Athena — CSV tables with DuckDB 2.0** — DuckDB 2.0's `type_pushdown` optimizer made the CSV reader's `TRY_CAST` strict, failing queries on values of another type; it is disabled on the Athena connection.
## [1.5.30] — 2026-10-20
diff --git a/pyproject.toml b/pyproject.toml
index c9067b30..987a2745 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
[project]
name = "ministack"
-version = "1.5.30"
+version = "1.5.31"
description = "Free, open-source local AWS emulator — drop-in LocalStack replacement"
readme = "README.md"
license = { file = "LICENSE" }