Five new services: Amazon Location, Signer, IoT Wireless, Translate and Lambda Core

September 10, 2026 · v1.5.10

v1.5.10 is a new-services release: Amazon Location, AWS Signer, IoT Wireless, Amazon Translate and Lambda Core all existed nowhere before this release, so a client bound to any of them failed at the first call. CloudFormation gains the Rules section and the AWS::Include transform, a REST method's COGNITO_USER_POOLS authorizer is now enforced, and EC2 subnets report AvailabilityZoneId.

New

• Amazon Location — trackers and device positions. CreateTracker and friends manage trackers, the four device-position operations serve positions, and AWS::Location::Tracker deploys. PositionFiltering applies: TimeBased stores one sample per 30 seconds per device, DistanceBased ignores a move under 30 m. Positions are held in memory, newest 100 per device. Contributed by @iot-rocket.
• AWS Signer — StartSigningJob with its S3 side effect. Signing is synchronous and synthetic, so the marker object lands at prefix + jobId before the call returns and a caller whose contract is the signed object never polls. Contributed by @iot-rocket.
• IoT Wireless — GetPositionEstimate. POST /position-estimate answers the way the API is shaped: the output structure declares a payload blob, so the body is the raw GeoJSON Point rather than a JSON envelope. Contributed by @iot-rocket.
• Amazon Translate — batch text translation jobs. StartTextTranslationJob, DescribeTextTranslationJob, ListTextTranslationJobs and StopTextTranslationJob run a job against the local S3 store. Contributed by @ppettitau.
• Lambda Core — network connectors. Terraform's aws_lambdacore_network_connector failed with Function not found because the service signs with Lambda's own credential scope and the path reached the function router. The five network-connector operations now serve /2026-04-04/network-connectors. Reported by @edersonbrilhante.
• CloudFormation — the Rules section and AWS::Include. A template's rules were ignored; they now run before any resource is touched, so the CDK's CheckBootstrapVersion rule refuses an outdated bootstrap instead of passing silently. An embedded Fn::Transform naming AWS::Include is replaced by the S3 object it points to. Contributed by @iot-rocket.

Fixes

• API Gateway — COGNITO_USER_POOLS is enforced. The v1 data plane matched only NONE, AWS_IAM and CUSTOM, so a method fronted by a user-pool authorizer served every caller and requestContext.authorizer.claims was never populated. The token is now verified against the pools in providerARNs. Contributed by @ppettitau.
• EC2 — subnets report AvailabilityZoneId. DescribeSubnets and CreateSubnet always returned null, and a consumer that recomputes the id can crash on that fallback. DescribeAvailabilityZones also reports ZoneType. Contributed by @Alexis-DevOps.
• EC2 — CreateFleet applies a launch template's instance tags. Fleet instances came back with an empty Tags list even though the template carried TagSpecifications, which is the mechanism AWS documents. Reported by @edersonbrilhante.
• Step Functions — numeric *Path Choice comparisons. NumericLessThanPath and its three siblings silently evaluated false, so a batch loop guarded by one never exited. Contributed by @jayjanssen.
• CloudFormation — template quotas and Capabilities. A template of any size or shape was accepted, so a template a real account refuses deployed; under AUTH=true a template with IAM resources now answers InsufficientCapabilitiesException. Contributed by @iot-rocket.
• SES — SendBulkEmail is routed. POST /v2/email/outbound-bulk-emails reached no handler. Contributed by @jgrumboe.

Upgrade

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

Or pin in compose.yaml:

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