Hi,
It looks like a recent update broke the ability to configure the AWS region where the environment variable SQS_AWS_REGION is ignored. I pulled the latest contain and it defaults to eu-central-1 ignoring what i have set in the docker compose file.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update dependency react-json-tree to ^0.19.0
• fix(deps): update material-ui monorepo to v5.16.7 (@mui/icons-material, @mui/material)
• chore(deps): update dependency @testing-library/react to v16
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Integrate contributors bot

Hey there, love the project!

Have you considered packaging sqs-admin as a LocalStack extension? They are a way to hook in third-party software that starts as part of LocalStack. Basically you could run the sqs-admin UI inside the LocalStack container and expose it through something like http://sqs-admin.localhost.localstack.cloud:4566.

Here's an example of what a web UI-based LocalStack extension looks like: https://github.com/thrau/localstack-aws-log-viewer

Extensions are part of the localstack pro edition, but we have hobby plan licenses that are free for non-commercial use of LocalStack which can be used for developing this. I'd be happy to help with this!

@all-contributors please add @PacoVK for review, projectManagement, maintenance, example.

Hey, I have sent more than 10 messages in the queue. However, the admin UI only shows 10 messages. I would like to continue seeing the message on the UI. Is this a missing feature? Or am I not configuring correctly? Thanks.

It would be nice if we can see the number of messages in each queue before clicking on it, because in the right side we'll only see the messages that aren't consumed yet. Wdyt?

(BTW tested the last changes and it's all good!)

when sending a message in the UI there is no option to introduce metadata (message attributes) would be nice to support it.

I'm facing the following issue when trying to update sqs-admin version from 0.5.3 to 0.5.4 and above:

2024/03/21 20:14:21 Got an error retrieving queue URLs: operation error SQS: ListQueues, exceeded maximum number of attempts, 3, https response error StatusCode: 500, RequestID: , deserialization failed, failed to decode response body, invalid character '<' looking for beginning of value

And with that, no queue is shown in the UI. The fix is just to downgrade to version 0.5.3 without changing anything else. I'm using localstack 1.3.1.

I was confused for a while just like #859 before I realized I was looking at queues in the wrong region. It might be helpful to show the current region for on the page to prevent it, as am sure a lot of people like me manage the same account in different regions. I can make the change and open a PR if you accept contributions. Thanks for the simple tool, works great with localstack.

Setup a contribution guide and generate contributors stats

Hello!

It'd be great if you allow sending messages to a FIFO queue, which requires the "MessageGroupId" parameter as mandatory in such cases.

BTW thanks for the repo

Using the package directly in the app could significantly improve the developer experience and, of course, reduce the code to maintain. I was doing some tests, and it can work, but the counterpoint is that Localstack needs to allow localhost URLs in the CORS settings (You can do it with an environment variable).
This change could open the door to porting the app to Electron.

What do you think? Could It be a good idea?

@all-contributors
please add @klutzer for code.
please add @stasadev for code.
please add @AlejandroPerez92 for code.
please add @PacoVK for review, projectManagement, maintenance, example.

Hi,

please change the environment variable AWS_REGION to SQS_AWS_REGION in the example docker compose file, as it is currently not working.

https://github.com/PacoVK/sqs-admin/blob/97d96dc4c31dea86197ac4a38af1ecaae673a224/example/docker-compose.yml#L9C7-L9C17

The backend API endpoint is hard-coded to http://localhost:3999.

There is no way to use a different host, and you cannot use a different HTTP_PORT if the frontend always points you to 3999.

Is it possible to add it to the list of env variables?

See:

• https://github.com/PacoVK/sqs-admin/blob/main/frontend/config.json

To ease development setup the following is required:
[] Makefile with dev commands (start UI and server and start required environment dependencies)
[] improve docs

I seemt o be getting a 500 eror with parsing while getting messages. Looks like create queue works fine but it just can't list the queues.

sqs-admin  | 2024/04/07 16:50:14 Got an error retrieving queue URLs: operation error SQS: ListQueues, exceeded maximum number of attempts, 3, https response error StatusCode: 500, RequestID: , deserialization failed, failed to decode response body, invalid character '<' looking for beginning of value

this is what I get when I run aws cli to list-queues

{
    "QueueUrls": [
        "http://169.254.170.9:4566/000000000000/PriceQueue.fifo",
        "http://169.254.170.9:4566/000000000000/PercentCalculateQueue",
        "http://169.254.170.9:4566/000000000000/PopularityQueue",
        "http://169.254.170.9:4566/000000000000/NewUserCreated"
    ]
}

Hi, I'm tryng to connect directly to AWS SQS endpoint,:

      - name: SQS_AWS_REGION
        value: "sa-east-1"  
      - name: SQS_ENDPOINT_URL
        value: "https://sqs.myregion.amazonaws.com"  
      - name: ACCESS_KEY
        value: "myaccesskey"   
      - name: SECRET_KEY
        value: "mysecretkey"

But i'm facing the error bellow

2024/04/25 11:03:10 Got an error retrieving queue URLs: operation error SQS: ListQueues, https response error StatusCode: 403, RequestID: 7e55994b-985d-5480-b26c-c7efa2f3a7f7, api error InvalidClientTokenId: The security token included in the request is invalid.

Is there a way to connect to AWS instead localstack?

Hello man!

Thanks again for the PR before.

Another thing I've noticed is when we work with a number of queues greater than 3: The tab list isn't filled up. I think we could probably use cards or even a list/table similar to elasticmq interface, wdyt?