SageMaker Endpoint Data Capture Disabled
Inputs and predictions are not recorded, so model drift and bad outputs cannot be investigated after the fact.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable data capture on SageMaker endpoint.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- SageMaker Endpoints on AWS
- The fix, by hand
- Create a new endpoint configuration with DataCaptureConfig enabled (set EnableCapture, a sampling percentage, and an S3 destination).
- Update the endpoint to use the new configuration.
- Optionally wire the captured data into SageMaker Model Monitor to baseline and schedule drift checks.
- Restrict the S3 destination bucket so captured payloads are encrypted and access-controlled.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1622- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.