Skip to content

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

release v1.5.30 (#2318)

Nahuel Nucerabeb431cebf46
diff --git a/CHANGELOG.md b/CHANGELOG.md
index e6946831..f51a58b2 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,8 @@ Versioning follows [Semantic Versioning](https://semver.org/).
## [Unreleased]
+## [1.5.30] — 2026-10-20
+
### Added
- **Auth — more calls are authorized under `AUTH=true`** — RDS Data calls are authorized as `rds-data:<operation>` on the cluster its `resourceArn` names, S3 Control `ListTagsForResource`, `TagResource` and `UntagResource` as `s3:<operation>` on the bucket, and SES v2 calls as `ses:<operation>` on the resource the path or create body names (`*` otherwise), each with AWS's 403 denial (`AccessDeniedException`, S3 Control `AccessDenied`) naming the action and resource. S3 bucket and identity policies now see `s3:x-amz-server-side-encryption` (a part and the completion take their `CreateMultipartUpload`'s), `s3:x-amz-acl`, `s3:x-amz-grant-*` and, on `GetObject` and `HeadObject`, `s3:ExistingObjectTag/<key>`. S3 Tables and Glue Iceberg REST calls at `/iceberg` are authorized for the catalog that serves them, whatever service they are signed for: on a table bucket as the `s3tables` actions AWS lists for the operation (`loadTable` needs `GetTableMetadataLocation`, then `GetTableData`) on the bucket or table (`table/*` for one that does not exist), on the Glue catalog as the route's `glue` action on the catalog, then the database, then the table, and `transactions/commit` as `updateTable` on each table it changes; a denial answers 403 in the Iceberg error shape naming the action and resource ("Access Denied" for a later S3 Tables action, no body for `HEAD`), a `{prefix}` that is neither a table bucket ARN nor `<account>:s3tablescatalog/<bucket>` answers 400 `bad_request`, and a call that names a key is served from its own region only. Contributed by @iot-rocket.
- **IoT — MQTT over WebSocket follows the signer's IAM policies under `AUTH=true`** — a session signed with an IAM user or STS key could connect under any client id and publish, subscribe and receive anywhere; its CONNECT, will, PUBLISH, SUBSCRIBE and deliveries now need `iot:Connect`, `iot:Publish` (and `iot:RetainPublish`), `iot:Subscribe` and `iot:Receive` on the client, topic and topic filter ARNs, with a certificate session's refusals. The handshake (and an `AWS_IAM` WebSocket `$connect`) has its signature, date and session token verified: IoT answers 403 `Forbidden` and expects the token after the signed part of the URL, API Gateway names the canonical string it expected, and the session runs in the signer's account. Contributed by @iot-rocket.
@@ -17,7 +19,7 @@ Versioning follows [Semantic Versioning](https://semver.org/).
- **API Gateway — credentials under `AUTH=true`** — a REST method with `NONE` or `COGNITO_USER_POOLS` authorization, or an HTTP API route without authorization, refused a signed caller its policies or signature failed; such a call now reaches the method and its own authorizer whatever it is signed with, and a REST API policy judges a `NONE` method's caller as anonymous (`ACCESS_DENIED` unless the policy allows everyone). A correctly presigned call (`X-Amz-Signature`) to an `AWS_IAM` method is served instead of 403 `MissingAuthenticationTokenException`. `CreateRestApi`, `GetRestApi`, `GetRestApis` and `UpdateRestApi` now return `apiStatus` `AVAILABLE` and `rootResourceId`, which Terraform AWS provider 6.x waits on. Contributed by @iot-rocket. Reported by @kharabasz.
- **AppSync — GraphQL authorization** — under `AUTH=true` a GraphQL call was authorized as `appsync:UpdateGraphqlApi` whatever the API's authentication type, and an `AWS_IAM` API served any `AWS4-HMAC-SHA256` header. On `/v1/apis/{apiId}/graphql` and on the API's own host an API key request now ignores its signature, and an `AWS_IAM` API needs a verified signature and authorizes `appsync:GraphQL` per top-level field (401 `Permission denied` when none is allowed, a field error per denied field, 400 `BadRequestException` for a wrong signature). Contributed by @iot-rocket.
- **AppSync — data-plane errors** — Event API `POST /event` refusals answered `{"__type", "message"}`, and GraphQL answered 500 for a body that is not a JSON object or a non-string `query` or non-object `variables`, a message-only 400 for a missing query and 200 for an unparseable one; both now answer AWS's `{"errors": [{"errorType", "message"}]}` envelope and `x-amzn-ErrorType` (`SerializationException`, `MalformedHttpRequestException`, `ResourceNotFoundException` for an unknown API or key, `UnknownOperationException` for another path on an Event API host), and publish answers `application/json`. Contributed by @iot-rocket.
-- **Cognito — tokens under `AUTH=true`** — `/oauth2/userInfo` returned the user's attributes for any JWT with a user's `sub`; it now refuses an ID token, an altered, revoked or expired token, a disabled or deleted user and a token without the `openid` scope with 401 `invalid_token`, AWS's `error_description` and a `WWW-Authenticate` realm of the pool's issuer. `AdminDisableUser` revokes the user's tokens (`User is disabled.`, then `Access Token has been revoked` / `Refresh Token has been revoked` and `invalid_grant` after `AdminEnableUser`), a deleted user's access token gets `UserNotFoundException: User does not exist.`, and refresh tokens are signature-checked and refused for a disabled user or a deleted user's successor. Contributed by @iot-rocket.
+- **Cognito — tokens under `AUTH=true`** — `/oauth2/userInfo` returned the user's attributes for any JWT with a user's `sub`; it now refuses an ID token, an altered, revoked or expired token, a disabled or deleted user and a token without the `openid` scope with 401 `invalid_token`, AWS's `error_description` and a `WWW-Authenticate` realm of the pool's issuer. `AdminDisableUser` revokes the user's tokens (`User is disabled.`, then `Access Token has been revoked` / `Refresh Token has been revoked` and `invalid_grant` after `AdminEnableUser`), a deleted user's access token gets `UserNotFoundException: User does not exist.`, and refresh tokens are signature-checked and refused for a disabled user or a deleted user's successor. ID tokens carry `email_verified` and `phone_number_verified` as JSON booleans, as AWS does; userInfo and the attributes keep them as strings. Contributed by @iot-rocket and @SAY-5. Reported by @proeben.
- **Cognito — identity `Logins` and OAuth scopes** — under `AUTH=true` `GetId`, `GetCredentialsForIdentity` and `GetOpenIdToken` took any token in `Logins`; they now refuse an unsupported provider, a token that is no ID token of a trusted client, a bad signature, one expired over five minutes or another user's login with `NotAuthorizedException` (`Access to Identity '<id>' is forbidden.` without `Logins`), `GetId` returns the identity that holds the login, and the first login is linked. A call on an identity without a login answers for the identity that holds its login, an identity with a login takes the logins of the identities holding the others, and a merged-away identity is listed with `["DISABLED", "<region>"]` (`ListIdentities` `HideDisabled` leaves it out). `/oauth2/authorize` with an `identity_provider` redirects with `error_description=invalid_scope` for a scope outside `AllowedOAuthScopes`, and `client_credentials` ignores undefined scopes once a defined one is requested (`api/read bogus/x` gets `api/read`). Contributed by @iot-rocket.
- **IoT — reserved MQTT topics** — a client could subscribe to any `$` filter and publish to the replies AWS IoT writes (fleet provisioning, Jobs, Device Defender, file delivery, Device Location, commands); the broker now refuses them before the policy check (SUBACK 0x8F, PUBACK 0x90 or DISCONNECT 0x90 at QoS 0, a closed connection on 3.1.1), judges a `$share/<name>/<filter>` subscription by its filter, and HTTPS `Publish` answers `Topic can't start with $` for fleet provisioning and Device Location replies. Contributed by @iot-rocket.
- **IoT — Jobs** — a stale `expectedVersion` answered 409 and now answers 400 `InvalidRequestException` (`VersionMismatch` over MQTT); a status a device may not set is refused first with `InvalidStateTransitionException`; a `statusDetails` that is not a string map answers 400 instead of 500, an execution has none until a device reports some, and an empty map replaces it; MQTT `get` and `update` answer `ResourceNotFound` for another `executionNumber`; describe and list calls time out expired executions; documents that are not JSON or nest over 1000 levels are refused; and Jobs MQTT messages are compact UTF-8 in AWS's member order, `clientToken` first, characters outside the BMP escaped, `"jobDocument":null` kept. Contributed by @iot-rocket.
diff --git a/pyproject.toml b/pyproject.toml
index 9c000872..c9067b30 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
[project]
name = "ministack"
-version = "1.5.29"
+version = "1.5.30"
description = "Free, open-source local AWS emulator — drop-in LocalStack replacement"
readme = "README.md"
license = { file = "LICENSE" }