Bedrock Imported Model Idle
An imported model bills for the custom model units it occupies while it remains ready to invoke.
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 idle imported 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 Imported Models on AWS
- The fix, by hand
- CloudWatch → Bedrock → InvocationCount on the imported model the resource. Confirm zero invocations over the lookback window.
- Confirm the source S3 model artefacts are still retained. You can re-import later if needed.
- Bedrock → Imported models → the resource → Delete.
- Audit your model lifecycle: tag imports with owner + project so the next round of cleanup is easier.
- The underlying S3 storage continues to bill. Apply lifecycle policy if those artefacts are also dormant.
ZopNight does this for you after a guided review.
- 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-1605- 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.