Tomasz Maruszak

The package is here: https://www.nuget.org/packages/SlimMessageBus.Host.AmazonSQS The docs are here: https://github.com/zarusz/SlimMessageBus/blob/release/v3/docs/provider_amazon_sqs.md

I need to find the time for SNS (unless the community is willing to take that on). Also, it helps prioritize SNS when I know folks need it.

Just a heads-up — I've started working on adding Amazon SNS support. I'll share an update here once a preview version is ready.

@jaap-van-yperen I have SNS around 80% done on a branch. I need to get back to it, finish, and then roll out. Let's aim for a release by 1st June...

There is a preview version available [SlimMessageBus.Host.AmazonSQS/3.2.1-rc100](https://www.nuget.org/packages/SlimMessageBus.Host.AmazonSQS/3.2.1-rc100) Documentation can be accessed from the [feature branch](https://github.com/zarusz/SlimMessageBus/blob/feature/amazon_sns/docs/provider_amazon_sqs.md). There is a PR #404. I plan to complete once I perform the final tweaks....

@jaap-van-yperen could you share a bus sample around this problem? > if you set up a Produce endpoint with a topic and a Consume endoint with a queue subscribed to...

@jaap-van-yperen The latest pre-release and the docs on the feature branch now include support for ambient (default) auth. Let me know if that works for you.

@jaap-van-yperen do you still have to specify the region explicitly, or is is it inferred automatically while inside fargate?

@jaap-van-yperen Thanks for sharing the sample. You're right—the issue stems from `SubscribeToTopic()`, which is specific to SNS and not compatible with the in-memory transport. When implementing the SNS feature, I...

Hi @jaap-van-yperen, I see the benefit in being able to switch seamlessly between SNS/SQS and in-memory transports. However, the current approach in the preview version makes it impossible: ```csharp .Consume(x...