-
### Describe the bug
When using `AWS_ENDPOINT_URL` together with `aws sqs`, it seems that specifically SQS commands are resolving `queue.amazonaws.com` as endpoint provider instead of what is speci…
thrau updated
3 months ago
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help…
-
In January 2023. AWS supported adding maximum concurrency on SQS lambda trigger. Details can be found here
https://aws.amazon.com/blogs/compute/introducing-maximum-concurrency-of-aws-lambda-functions…
-
### Why is this issue important?
Developers have to manually create and maintain the treasury report queue and there is not much documentation on how to do so.
### Current State
To test the ARPA tr…
-
Taking in the queue name instead of its url is an unfortunate choice, as it takes another SQS API call to figure out the queue url from its name, and this API call is covered by a dedicated permission…
-
### What happened?
Deploy AWS SNS and SQS with `pulumi up` always results in subscription not working. At the moment, I find myself going to the SQS dashboard and manually subscribing to SNS topic to…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current Behavior
Create an event bridge pipe with the following:
- Source: DynamoDB
- Target: SQS FI…
-
If I subscribe an SQS queue to an SNS topic using the "subscribe_sqs_queue" method, unsubscribe the queue and then subscribe the queue again using the same "subscribe_sqs_queue" method I get the error…
-
# Checklist
- [x] I have verified that the issue exists against the `main` branch of Celery.
- [x] This has already been asked to the [discussions forum](https://github.com/celery/celery/discuss…
-
### Issue description
Setting `maximumConcurrency` as described [here](https://www.serverless.com/framework/docs-providers-aws-events-sqs#setting-the-maximum-concurrency) produces this warning when u…