Lambda layer site-packages, CloudFormation deploy detection + SubscriptionFilter, and Step Functions mock fixes

June 13, 2026 · v1.3.63

v1.3.63 is a fixes release — seven AWS-parity corrections across Lambda, CloudFormation, and Step Functions, every one driven by a reported issue or a contributed PR.

Lambda

• Local executor exposes dependency layers' site-packages. The in-process Python worker added <layer>/python to sys.path but not <layer>/python/lib/python<ver>/site-packages, so pip install -t dependency layers failed to import (the docker executor, which runs the AWS runtime image, was unaffected). AWS exposes that path as a site directory, so MiniStack now adds it via site.addsitedir — meaning .pth files and namespace packages resolve too, not just flat modules. Reported by @omargr299.
• LoggingConfig.LogGroup is honored when emitting CloudWatch logs. Handler output was always written to the default /aws/lambda/<name> group instead of the configured or shared log group named in LoggingConfig. Reported by @ankitaabad.

CloudFormation

• AWS::Logs::SubscriptionFilter resource type supported. Templates using it no longer fail with Unsupported resource type; the filter provisions against the named log group and is removed on stack delete. Reported by @ankitaabad.
• Change sets detect parameter-driven property changes. aws cloudformation deploy silently no-oped when a property such as a Lambda Code S3 key was driven by a stack parameter, because the change-set diff compared unresolved templates — identical Ref nodes look unchanged even when the parameter value differs. The diff now resolves parameters and intrinsics before comparing, matching update-stack. Reported by @ankitaabad.
• DescribeStackResources honors the LogicalResourceId filter. The handler now reads the optional LogicalResourceId parameter and, when present, returns only the matching resource — or a ValidationError if it does not exist in the stack. Contributed by @maximoosemine.

Step Functions

• Assign is applied in the mock execution path for JSONata Task states. When SFN_MOCK_CONFIG was active, _apply_state_assign was never called on the mock return branch, so any Assign block in a JSONata Task state was silently skipped and downstream states referencing the assigned variables failed with States.QueryEvaluationError: Undefined variable. The mock branch now mirrors the real execution path. Contributed by @amissemer.
• Pass state Parameters resolve context object paths. $$.* references resolved to null in Pass states because the executor applied Parameters without forwarding the execution context; it now forwards the context correctly. Contributed by @noynoy83.

Upgrade

docker pull ministackorg/ministack:1.3.63
docker run -d -p 4566:4566 ministackorg/ministack:1.3.63

Or pin in compose.yaml:

services:
  ministack:
    image: ministackorg/ministack:1.3.63
    ports:
      - "4566:4566"