Which action will remediate this issue?
Change the scaling policy to scale based upon the number of messages in the queue.
Decouple the queue from the Elastic Beanstalk worker node and create it as a separate resource.
Increase the number of messages in the queue.
Increase the retention period of the queue.
Explanations:
Scaling based on the number of messages in the queue will directly address the issue of increasing messages, ensuring that more worker nodes are added when the queue backlog increases.
Decoupling the queue from the Elastic Beanstalk worker node does not address the scaling issue and would complicate the architecture without resolving the message backlog problem.
Increasing the number of messages in the queue would only exacerbate the problem. The issue is not the number of messages but the system’s inability to process them quickly enough.
Increasing the retention period would simply allow messages to stay in the queue longer without solving the issue of processing and scaling to meet demand.
As far as I can tell, the answer is:
Change the scaling policy to scale based upon the number of messages in the queue.
I suspect that the answer is:
Change the scaling policy to scale based upon the number of messages in the queue.