When installing Appsmith on AWS ECS using this setup guide, the task may get stuck in a pending state. This article explains how to troubleshoot such issues.
The issue is caused by a small configuration mistake on the user's side.
To diagnose this issue, you need to grab the server logs and check the error message returned:
Stopped reason Error response from daemon: create ecs-appsmith_task-1-appsmith_stack-...: Post "http://%2Frun%2Fdocker%2Fplugins%2Famazon-ecs-volume-plugin.sock/VolumeDriver.Create": context deadline exceeded
Another error you may notice when checking the events from the service is:
service appsmith-prod was unable to place a task because no container instance met all of its requirements. The closest matching container-instance .... has insufficient memory available. service appsmith-prod was unable to stop or start tasks during a deployment because of the service deployment configuration. Update the minimumHealthyPercent or maximumPercent value and try again.