Idle SageMaker Endpoint, No Invocations
A real-time endpoint bills for its instances from the moment it reaches InService until it is deleted, regardless of invocations.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Delete the idle SageMaker endpoint. Where the saving can be proven it is priced; where it cannot, the finding says so.
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
- Confirm no application is invoking this endpoint (check CloudWatch Invocations).
- If a model must stay deployable, migrate to a serverless endpoint (pay-per-inference).
- Otherwise delete the endpoint to stop instance charges.
- Clean up the associated endpoint config and unused models.
These are the steps the finding carries in the product.
- Category
- Idle resources. Resources running but doing no useful work: zero invocations, no connections, no traffic.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1613- Full reference
Related checks
See the idle resources 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.