During council week, a PDF generation service on Elastic Beanstalk or ECS falls behind because tasks were sized with too little CPU. What should developers declare for the artifact?
Select an answer to reveal the explanation.
Short Explanation
If the oven is too small, the pizza backlog is not a messaging bug. Size Beanstalk instances or ECS task CPU/memory for council-week PDF spikes, then tune queues. Stretching visibility timeouts alone will not mint missing cores.
Full Explanation
Preparing application artifacts includes declaring resource requirements such as memory and CPU for Elastic Beanstalk environments or ECS task definitions. Under-provisioned compute causes queue backlog even when messaging is healthy. Developers should right-size CPU/memory for expected municipal peak load and monitor utilization. Visibility timeout tweaks, artificial single-worker limits, or mock integrations do not satisfy the resource-requirement skill.