EKS DescribeCluster endpoint and SQS XML message validation fixes

June 27, 2026 · v1.3.69

v1.3.69 is a fixes release: EKS DescribeCluster now returns a host-reachable endpoint on every path, and SQS rejects message bodies containing XML 1.0 forbidden characters — both closing AWS-parity gaps.

EKS

• DescribeCluster returns a host-reachable endpoint on every path. DescribeCluster now advertises the host-published port https://{MINISTACK_HOST}:{port} (MINISTACK_HOST defaults to localhost) uniformly on cluster create, OIDC-config restart, and persistence restore. Previously the failure-fallback and restore paths could leave a stale value, so aws eks update-kubeconfig + kubectl from the host got an unreachable endpoint. The k3s container publishes 6443 to that host port (ports={"6443/tcp": port}), so the endpoint works from the host and from containers that can route to MINISTACK_HOST, keeping the ACTIVE-cluster shape consistent for aws eks update-kubeconfig and Terraform. Contributed by @b-rajesh.

SQS

• SendMessage rejects message bodies with XML 1.0 forbidden characters. AWS SQS only accepts characters valid in XML 1.0 and returns InvalidMessageContents for anything else; MiniStack silently accepted them, so a payload that fails against real AWS passed locally. SendMessage (and every SendMessageBatch entry) now rejects bodies containing C0 control characters other than tab/LF/CR, the surrogate block #xD800–#xDFFF, and #xFFFE/#xFFFF with InvalidMessageContents. Contributed by @yamachu.

Upgrade

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

Or pin in compose.yaml:

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