You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I read the page about SQS and Celery ( https://docs.celeryq.dev/en/stable/getting-started/backends-and-brokers/sqs.html ) and I notice that it wasn't mentioned if it is possible to use a different endpoint URL for the SQS API.
This is required if you want to use another cloud provider that provide a SQS compatible API, and also to test locally using a queue that expose a SQS compatible API like ElasticMQ.
For exemple, in boto3 you can use the property endpoint_url to set it up:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I read the page about SQS and Celery ( https://docs.celeryq.dev/en/stable/getting-started/backends-and-brokers/sqs.html ) and I notice that it wasn't mentioned if it is possible to use a different endpoint URL for the SQS API.
This is required if you want to use another cloud provider that provide a SQS compatible API, and also to test locally using a queue that expose a SQS compatible API like ElasticMQ.
For exemple, in
boto3
you can use the propertyendpoint_url
to set it up:Is it possible by adding a specific key in
broker_transport_options
or by setting up an environment variable likeAWS_ENDPOINT_URL_SQS
?Beta Was this translation helpful? Give feedback.
All reactions