Transport preview · Amazon Web Services
Amazon SQS/SNS, with a deliberately narrow compatibility promise.
MyServiceBus uses standard SQS queues for directed delivery and SNS topics with raw SQS subscriptions for publication. C# and Java follow the same MassTransit-oriented transport profile.
Directed sends and publications pass in both directions between MassTransit 8.5.1 and the C# and Java clients on LocalStack. A separate, manual AWS run verifies topology creation, delivery, settlement, and exact-resource cleanup.
Verified to work
- Standard SQS queue creation and directed delivery
- SNS publication through raw SQS subscriptions
- MassTransit-compatible message envelopes and default topic names
- MassTransit 8.5.1 ↔ MyServiceBus C# in both directions
- MassTransit 8.5.1 ↔ MyServiceBus Java in both directions
- Visibility renewal and successful receive/delete settlement
Not verified or supported
- FIFO queues, ordering, message groups, or deduplication
- MassTransit versions other than 8.5.1
- Cross-region SNS-to-SQS delivery
- Every MassTransit middleware, saga, scheduler, routing-slip, or persistence feature
- Production-scale throughput, throttling, and resilience characteristics
Topology used by the preview
A durable endpoint uses one SQS queue, companion _error and _skipped queues, SNS topics for consumed contracts, raw SNS subscriptions, and a least-privilege queue policy. Infrastructure-owned environments can select pre-provisioned topology mode.
LocalStack is the default acceptance environment. The AWS account is used only for a documented emulator limitation, an observed discrepancy, or an AWS-only concern such as IAM. Portable pipeline behavior belongs to the shared suites.