bug: Cannot create an SQS queue with FifoQueue: false

[JavaScriptBach]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I can't create an SQS Queue using the AWS JavaScript SDK with FifoQueue: "false". Attempting to do so gives an error of InvalidAttributeName: Unknown Attribute FifoQueue and metadata saying that localstack responded with a 400.

Expected Behavior

The queue is created successfully.

How are you starting LocalStack?

With a docker-compose file

Steps To Reproduce

How are you starting localstack (e.g., bin/localstack command, arguments, or docker-compose.yml)

docker-compose.yml

Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)

const sqs = new SQSClient({ endpoint: "http://localstack:4566", credentials: { accessKeyId: "foo", secretAccessKey: "bar", }, region: "us-east-1" });

await sqs.send(
    new CreateQueueCommand({
      QueueName: "test-queue",
      Attributes: {
        FifoQueue: "false",
      },
    }),
  );

Environment

- OS: Ubuntu 22.04
- LocalStack: 3.4.0
- @aws-sdk/client-sqs version: 3.370.0

Anything else?

No response

[localstack-bot]

Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.

[cloutierMat]

Hi @JavaScriptBach,

This is actually the behaviour observed with aws. Trying to create a queue with the FifoQueue attribute does result in an error.

▶ aws sqs create-queue --queue-name my-queue --attributes "{\"FifoQueue\":\"false\"}"

An error occurred (InvalidAttributeName) when calling the CreateQueue operation: Unknown Attribute FifoQueue.

This is a well known "issue" and the recommended approach is to either not set the attribute at all or to set it as undefined. Looking into it, I realised that Localstack was allowing for the original creation with the attribute set but wasn't allowing subsequent create_queue calls.

I just opened a PR that will bring parity with AWS behaviour.