What's Changed
New Contributors
[1.3.32] — 2026-05-09
Added
- EC2 VPN Connection support —
CreateVpnConnection,DescribeVpnConnections,DeleteVpnConnection,CreateVpnConnectionRoute,DeleteVpnConnectionRoute. StoresType,CustomerGatewayId,VpnGatewayId,TransitGatewayId,Options.StaticRoutesOnly, and per-connectionRoutes. Contributed by @tmq107.
Fixed
- Cognito OIDC autodiscovery —
/.well-known/openid-configurationnow returns reachable endpoint URLs at the MiniStack gateway instead of unreachablecognito-idp.{region}.amazonaws.comURLs that don't serve OAuth2 anywhere.response_types_supportednow advertises bothcodeandtoken, matching real AWS Cognito. Amplify and other OIDC clients can now auto-configure against MiniStack without manual endpoint setup. Reported by @coezbek. - Cognito OAuth2 / OIDC endpoints send CORS —
/oauth2/authorize,/oauth2/token,/oauth2/userInfo,/logout, and/.well-known/*were returning raw response tuples that bypassed_with_data_plane_headers, so browser-based OIDC clients (Amplify,oidc-client-ts,react-oidc-context) failed cross-origin discovery and token exchange withNo 'Access-Control-Allow-Origin' header. The dispatchers are now routed through the same wildcard-CORS wrapper every other data-plane response uses. Contributed by @coezbek. - EC2
RunInstanceshonorsPrivateIpAddressandIamInstanceProfile—--private-ip-addresswas ignored and the auto-generated default IP was malformed (10.0193.216from a missing dot separator in_random_ip).--iam-instance-profilewas dropped entirely, so the launched instance had noIamInstanceProfilefield inRunInstancesorDescribeInstances. Both parameters are now stored on the instance record and emitted in the XML response (<iamInstanceProfile><arn/><id/></iamInstanceProfile>). Reported by @coseym. - EC2
DescribeRouteTablesemitspropagatingVgwSet—EnableVgwRoutePropagationstored the gateway ID on the route table butDescribeRouteTablesalways returned an empty<propagatingVgwSet/>, so any IaC tool that round-trips through Describe lost the propagation. Now serializes whateverEnableVgwRoutePropagationrecorded. Contributed by @tmq107. - DynamoDB GSI Query pagination with non-unique sort keys — when multiple items shared the same
(GSI_HASH, GSI_RANGE)value (or for hash-only GSIs),ExclusiveStartKeyeither dropped items silently from page 2 onward or cycled the caller through the same items indefinitely. Real DynamoDB orders GSI results by(INDEX_HASH, INDEX_SORT, BASE_PK, BASE_SK); MiniStack now uses the same hidden tiebreak so cursors advance correctly across pages. Common pattern with single-table designs / ElectroDB collections. Reported by @bensont1 and @mspiller.