Bedrock Custom Model Orphan
A custom model is billed for storage for as long as it exists, and one no provisioned throughput or agent references cannot be invoked at all.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, fixed.
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 undeployed custom model. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
After a guided review, where you confirm the change, ZopNight deletes the resource, then checks the change took.
- Applies to
- Bedrock Custom Models on AWS
- The fix, by hand
- Bedrock → Custom models → the resource → review last-invoked timestamp and the training run that produced it.
- If retention is needed for compliance or future re-use: export the model artefacts to S3 (custom models have an output S3 prefix from training).
- Confirm no production application still calls this custom model ARN.
- Bedrock → Custom models → Actions → Delete.
- Audit your fine-tuning pipeline so the next round of customs gets tagged with owner + retention class.
ZopNight does this for you after a guided review.
- Category
- Orphaned resources. Resources no longer attached to anything that needs them, such as unattached volumes and unassigned IPs.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1604- Full reference
Related checks
See the orphaned 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.