github ministackorg/ministack v1.5.43

32 minutes ago

What's Changed

New Contributors

[1.5.43] — 2026-11-19

Added

  • Cognito — app client secret rotation — AddUserPoolClientSecret, ListUserPoolClientSecrets and DeleteUserPoolClientSecret. A client holds at most two secrets, each with an ID of <ClientId>--<epoch ms>. A generated secret is 51 lowercase letters and digits. SECRET_HASH, the token endpoint and GetTokensFromRefreshToken accept either active secret. A third gives LimitExceededException "Client secrets cannot exceed limit of 2 secrets.", deleting the last one gives InvalidParameterException "Cannot delete the only client secret.", and an unknown ID gives ResourceNotFoundException "Client secret does not exist". Once the original secret is deleted, DescribeUserPoolClient no longer shows a ClientSecret. Reported by @TheKerbycz.
  • Cognito — POST /oauth2/revoke — revokes a refresh token and the tokens issued from it, so a later refresh fails with NotAuthorizedException "Refresh Token has been revoked". It takes a form body only (otherwise 415 with an empty body). A missing token answers 400 invalid_request "Invalid parameter in request", and a bad client secret answers 401 invalid_client "Invalid client credentials in request". An unknown token, or one already revoked, answers 200 with an empty body. Reported by @TheKerbycz.

Fixed

  • Kinesis — CBOR timestamps past the year 9999 — a CBOR request carrying an epoch timestamp beyond 9999-12-31, such as the millisecond StreamCreationTimestamp the Kinesis Client Library sends in multi-stream mode, failed whole with SerializationException. CBOR timestamps now reach the handlers as epoch numbers, as JSON ones do, which also fixes GetShardIterator AT_TIMESTAMP over CBOR. Reported by @tabili4.
  • Kinesis — calls slowed as a stream grew — every put and read rebuilt each shard's whole record list to drop expired records, so a stream holding 200,000 records spent ~13 ms per call on it. Expiry now trims only the expired records at the front. Reported by @TLDart.
  • Aurora DSQL — isolation levels — with DSQL_STRICT=1, a transaction could begin at READ COMMITTED or SERIALIZABLE, and a plain BEGIN ran at Postgres's read committed. Every transaction now runs at repeatable read. Any other level in BEGIN, START TRANSACTION, SET TRANSACTION or SET SESSION CHARACTERISTICS is refused 0A000 "Unsupported isolation level: …", and default_transaction_isolation and transaction_isolation can no longer be set, as on the live service. Reported by @toby6578.
  • Cognito — OIDC provider endpoints with a query — an OIDC provider whose authorize_url, token_url, attributes_url, jwks_uri or oidc_issuer has a query string is refused with InvalidParameterException "Endpoint can not contain queries" on create and update. Reported by @TheKerbycz.
  • Cognito — federated sign-in — /oauth2/authorize without identity_provider, for a client whose only provider is an external one, now redirects straight to that IdP. When the IdP's token endpoint refuses the code, the user returns to the app's redirect_uri with error=invalid_request and error_description " Error - <error_description>". An unreachable token host gives the host name as the description. Before, the user got a Cognito error page. An OIDC user now stores only the claims the attribute mapping names, and email_verified is false unless it is mapped. Reported by @TheKerbycz.
  • IAM — aws:PrincipalArn and aws:PrincipalIsAWSService — for a role session, aws:PrincipalArn is now the role's ARN with its path, not the session ARN. aws:PrincipalIsAWSService is false on a direct call; before, it was missing, so a Bool condition on it never matched. Reported by @TheKerbycz.
  • DynamoDB — dynamodb:LeadingKeys — with AUTH=true, the partition key values of GetItem, PutItem, UpdateItem, DeleteItem, Query, BatchGetItem, BatchWriteItem and the transaction items are now in the condition context. A ForAllValues:StringEquals policy on them limits each caller to its own keys, and a refusal is 400 AccessDeniedException. Reported by @TheKerbycz.
  • S3 — expected bucket owner — x-amz-expected-bucket-owner and x-amz-source-expected-bucket-owner were ignored. When the bucket belongs to another account, the request now answers 403 AccessDenied "Access Denied". A value that is not a 12-digit account ID answers 400 InvalidBucketOwnerAWSAccountID. Reported by @TheKerbycz.
  • S3 — SSE-KMS needs KMS permissions — with AUTH=true, writing an object under a customer managed key (put, copy, multipart create) also needs kms:GenerateDataKey on the key. Reading it (get, copy source) needs kms:Decrypt. A refusal is 403 AccessDenied "User: is not authorized to perform: kms:GenerateDataKey on resource: because no identity-based policy allows the kms:GenerateDataKey action". Reported by @TheKerbycz.
  • Secrets Manager — RotateSecret runs the rotation function — RotateSecret copied the current value into a new AWSCURRENT version itself, and the function was never invoked. It now invokes the function with createSecret, setSecret, testSecret and finishSecret. Each event carries ClientRequestToken, RotationToken, SecretId and Step. The function moves the stages, and the call answers with the new VersionId. With RotateImmediately false, only testSecret runs. Reported by @TheKerbycz.
  • Cognito — AdminLinkProviderForUser source provider — a SourceUser.ProviderName that is not an identity provider of the pool is refused with 400 InvalidParameterException SourceProviderName must match a Provider that is configured for the User Pool, and the user keeps its identities. Contributed by @emreocell. Reported by @TheKerbycz.
  • Cognito — SupportedIdentityProviders of an app client — CreateUserPoolClient and UpdateUserPoolClient refuse a name that is neither COGNITO nor an identity provider of the pool with 400 InvalidParameterException The provider <name> does not exist for User Pool <pool id>., naming the first missing name in list order; the match is case-sensitive, also for COGNITO. The client is not created or changed. Create the identity provider before the client that names it. Contributed by @emreocell. Reported by @TheKerbycz.
  • RDS — CreateDBCluster status — the CreateDBCluster response reported Status available. It now reports creating, as AWS does. DescribeDBClusters still reports the status from the cluster's members, so a cluster with no members is available at once. Contributed by @Areson.
  • ECR — pull-through cache rule for an ECR upstream in the same account — CreatePullThroughCacheRule for an ECR upstream in the caller's account and another region asked for a customRoleArn, and refused one with "Upstream registry URL and provided credential type do not match", so the rule could never be created. It is now created without a role, as on AWS, and the first pull copies the upstream image without one. Rules for an upstream in another account are unchanged. Contributed by @kharabasz.

Don't miss a new ministack release

NewReleases is sending notifications on new releases.