Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add Boto3 support for use with SQS
See original GitHub issueWe are running Celery on AWS and using SQS to provide the queue. We use boto3 in other parts of the project and would prefer not to effectively duplicate dependancies by including both boto and boto3.
I would like to work towards adding support for boto3 into Kombu in such a way that both boto and boto3 can be used interchangeably(along the lines of tying boto3 and falling back to boto). Is this be something that the project is interested in?
I have not investigated too deep into this, and will try to investigate this week.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Without this we can’t easily run Celery on ECS using TaskRoles, which means that we need to set an IAM Role for the instance instead of the task, giving permission to all containers in those instances to access our celery queues.
Unfortunately I am not familiar with the kombu codebase so I won’t be able to work on this myself.
https://github.com/celery/kombu/commit/129a9e4ed05bf9a99d12fff9e17c9ffb37b14c4d