Is there a single point of failure? If yes, how can it be improved or mitigated?
Yes, for silent data loss: step 3, the memory batch. The endpoint has already accepted the event. The 20-minute job has not seen a file yet. A deploy, an out-of-memory kill, or a task replacement drops the batch, and the warehouse stays green because there was nothing to copy. S3, the manifest job, and Redshift can all retry a file that exists. They cannot retry a batch that lived only in RAM.
That is the only place an accepted event can disappear without leaving a file. Mitigate it before any stream: the process may forget a batch only after the JSON is on S3, and it flushes on shutdown. Client retry covers a short endpoint blip. Two ECS tasks so one death is not a collection outage. Detail and the diagram of the fix are under What changes.