2022.09.27 12:01:16 INFO app[][o.s.a.SchedulerImpl] Stopping SonarQube
2022.09.27 12:01:16 INFO app[][o.s.a.SchedulerImpl] Sonarqube has been requested to stop
2022.09.27 12:01:16 INFO app[][o.s.a.SchedulerImpl] Stopping [Compute Engine] process...
2022.09.27 12:01:16 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [Compute Engine]: 143
2022.09.27 12:01:16 INFO app[][o.s.a.SchedulerImpl] Process[Compute Engine] is stopped
2022.09.27 12:01:16 INFO app[][o.s.a.SchedulerImpl] Stopping [Web Server] process...
2022.09.27 12:01:16 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [Web Server]: 143
2022.09.27 12:01:16 INFO app[][o.s.a.SchedulerImpl] Process[Web Server] is stopped
2022.09.27 12:01:16 INFO app[][o.s.a.SchedulerImpl] Stopping [ElasticSearch] process...
2022.09.27 12:01:16 INFO app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2022.09.27 12:01:16 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 143
2022.09.27 12:01:16 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
So it sounds like ECS is terminating the task (close to Noon, perhaps a coincidence). I would look into what is set around scheduling/orchestration in ECS to understand why it’s happening – right now, it doesn’t look like SonarQube itself is involved.