What is the difference between running containers in Elastic Beanstalk and ECS?

Question

Amazon Web Services

What is the difference between running containers in Elastic Beanstalk and ECS ?

Situations:
1) one container with an application that I access from a local application
2) The local application is finalized, launched as a separate container and will sometimes access the first

container The second container also accesses the database in RDS (the third application also accesses it, but it's just a Flask website running in Beanstalk as a WSGI application)
Or maybe it's better to make a container for everyone and run it in a cluster? (but I'm already moving away from the main question)

Answer 1

EB and ECS are completely different services. EB was created to simplify the deployment procedure, and ECS to deploy the infrastructure. EB for containers works as a wrapper around ECS. Of course, working directly with ECS is more promising, but also more difficult.
How to run containers is absolutely up to you. It depends on the tasks and nature of the application, but the fact that you have several containers working with the same database already hints that you have problems