1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa