don1uppa opened a new issue, #22863: URL: https://github.com/apache/airflow/issues/22863
### What do you see as an issue? https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#celery-broker-transport-options This section is for specifying options which can be passed to the underlying celery broker transport. See: http://docs.celeryproject.org/en/latest/userguide/configuration.html#std:setting-broker_transport_options So I want to use sqs (fifo) for my celery queue , I can't determine how to fill out this section. Tried this: [celery_broker_transport_options] predefined_queues = { "default": { "region": "us-east-1", "url": "https://sqs.us-east-1.amazonaws.com/xxxx/asg-airflow-dev-queue.fifo";, "MessageGroupId": "1", "MessageDeduplicationId": "123" }} The https://docs.celeryq.dev/en/latest/getting-started/backends-and-brokers/sqs.html document shows this: **broker_transport_options** = { 'predefined_queues': { 'my-q': { 'url': 'https://ap-southeast-2.queue.amazonaws.com/123456/my-q', 'access_key_id': 'xxx', 'secret_access_key': 'xxx', 'backoff_policy': {1: 10, 2: 20, 3: 40, 4: 80, 5: 320, 6: 640}, 'backoff_tasks': ['svc.tasks.tasks.task1'] } }, 'sts_role_arn': 'arn:aws:iam::<xxx>:role/STSTest', # optional 'sts_token_timeout': 900 # optional, message_properties = { 'MessageGroupId': '<YourMessageGroupId>', 'MessageDeduplicationId': '<YourMessageDeduplicationId>' } } The closest think I can find is in this but it uses AIRFLOW__CELERY__CELERY_CONFIG_OPTIONS which is also not explained. https://github.com/apache/airflow/issues/20947 ### Solving the problem add necessary example ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
