1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 7 Monaten