Existing check search
Provider
AWS
New provider name
No response
Service or product area
sagemaker
Suggested check name
sagemaker_models_monitor_enabled
Context and goal
- Security condition to validate: At least one SageMaker monitoring schedule exists in the account/region and is in Scheduled status.
- Why it matters: Model Monitor detects data drift, model quality issues, and bias drift in production. Without active monitoring, model degradation goes undetected and downstream decisions (fraud, access, pricing) silently degrade.
- Resource involved: SageMaker monitoring schedule (MonitoringScheduleStatus, MonitoringType).
Expected behavior
- Resource or scope to evaluate: SageMaker monitoring schedules in the account/region.
- PASS when: at least one monitoring schedule exists and its status is Scheduled.
- FAIL when: no monitoring schedule exists, or all existing schedules are in Pending, Failed, or Stopped status.
References
Suggested severity
Low
Additional implementation notes
No response
Existing check search
Provider
AWS
New provider name
No response
Service or product area
sagemaker
Suggested check name
sagemaker_models_monitor_enabled
Context and goal
Expected behavior
References
Suggested severity
Low
Additional implementation notes
No response