1 Answer
- Newest
- Most votes
- Most comments
0
Are you already using a scheduler in your existing infrastructure that you're trying to migrate? The easiest way would be to keep using your current one.
AWS batch isn't a generic job scheduler but rather a service that orchestrates AWS compute running jobs packaged as containers, it also doesn't have an elaborated graphical interface that would be similar to what's there in Control-M.
The MWAA is dedicated to Apache Airflow orchestration and isn't a generic job scheduler either.
Regards
answered 2 years ago
Relevant content
- asked 2 years ago
- asked 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago