Bad Request returned for SQS operations when using the .NET SDK

[attilah]

We tried to use the tool with AWS .NET SDK and we received Bad Request response.

Sample code:

using Amazon.Runtime;
using Amazon.SQS;

var service = "http://localhost:4566/";
var credentials = new BasicAWSCredentials("dummy", "dummyKey");
var sqsClient = new AmazonSQSClient(credentials, new AmazonSQSConfig { ServiceURL = service});

try
{
    var response = await sqsClient.CreateQueueAsync($"foobar-0-{Guid.NewGuid()}");

    Console.WriteLine(response.QueueUrl);
}
catch (AmazonSQSException ex)
{
    Console.WriteLine(ex);
}

A discrepancy that I saw that when tried to create the same queue with AWS CLI it worked, but the returned queue url is invalid as a Url:

{
  "QueueUrl": "http://://foobar-0"
}

While with localstack it is more lifelike:

{
  "QueueUrl": "http://sqs.us-east-1.localhost.localstack.cloud:4566/000000000000/foobar-1"
}

[sofiagvaladze]

Same here with ruby, seems to be broken since: https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-sdk-core/CHANGELOG.md#31920-2024-04-16 (didn't check minor versions but 3.191 works fine)

[Admiral-Piett]

@attilah Can you try it with v0.5.0? It's likely these issues are do to an SDK'S upgrade to AWS JSON 1.1 protocol, which we should support as of v0.5.0.

[attilah]

@Admiral-Piett sure, we're giving it a try, thanks!

[attilah]

It seems to be working with AWS CLI and the .NET SDK as well, thank you!