Bedrock Custom Model Deployment Unused
A provisioned deployment is billed for its capacity whether or not anything calls it.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
What we would change and why, with no savings claim and no policy behind it.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Delete the unused custom model deployment.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Bedrock Custom Model Deployments on AWS
- The fix, by hand
- Confirm no application invokes this custom model deployment.
- Verify the underlying custom model artifact is retained if still needed.
- Delete the custom model deployment via the Bedrock console.
- Re-deploy on demand from the custom model when next needed.
These are the steps the finding carries in the product.
- Category
- Advisory. Findings worth knowing about that carry no dollar figure and no one-click action. Each comes as a numbered playbook.
- Where it appears
- The Advisory tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1634- Full reference
Related checks
See the advisory 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.