Skip to content

Tested versions

The adapter's suite runs against LocalStack 4.14.0, in a container. It does not run against AWS.

Thing Version Where it is recorded
LocalStack 4.14.0 (localstack/localstack:4.14.0) image in test/integration/main_test.go
LocalStack region and credentials us-east-1, static test / test awsConfig in test/integration/main_test.go
container runner testcontainers-go v0.44.0, and its LocalStack module v0.44.0 go.mod
AWS SDK for Go v2 v1.47.4 go.mod
service/sqs v1.52.6 go.mod
service/sns v1.47.6 go.mod
credentials v1.20.11 go.mod
config v1.33.9 (indirect) go.mod
smithy-go v1.28.7 go.mod
go/messaging, the core v0.9.0 go.mod
go/awsclient v0.1.2 go.mod
go/envelope v0.1.0 go.mod
go/envelope-cloudevents v0.1.0 go.mod
go/envelope-masstransit v0.1.0 go.mod
go/envelope-nservicebus v0.1.0 go.mod
Go 1.27.3 go directive in go.mod

These are the versions on main. A release pins whatever main held when it was cut.

Why LocalStack 4.14.0

The image is pinned to the last community tag that starts without an auth token. A later LocalStack needs one.

Where LocalStack differs from AWS

LocalStack Consequence
does not enforce an SQS queue's access policy the policy the adapter writes on its own queue, and the one you write, are untested
does not enforce SNS's rule that a message is UTF-8 the adapter enforces it itself at Publish, so the two agree
keeps nothing across a container restart the suite's Restart does nothing at the service. What it proves is that a consumer's restart loses no message and no attempt count
delivers a FIFO topic's backlog far slower than it accepts publishes the fixture waits for it to drain between rows
expires visibility about a second late the fixture states a two-second lease granularity

The measurement that SQS enforces its twelve-hour visibility cap per call on FIFO and from the receive on Standard was taken on AWS, on 2026-10-12, and is recorded in the core's specs. It is a measurement of SQS's behaviour that day, against AWS's own documentation of the cap for both.

What runs

Eight suites: the durable conformance suite under FIFO and Standard, each with CloudEvents binary, CloudEvents structured, MassTransit and NServiceBus as the writer. Alongside them are the adapter's own checks. See Run the conformance suite.

Real AWS

Nothing in the repository's pipeline runs against AWS. The unit gate needs no AWS or Docker.