Bedrock Custom Model Without CMEK
The model artifacts are encrypted with a key you do not control, so access cannot be revoked independently.
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: Encrypt the custom model with a customer-managed key.
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 Models on AWS
- The fix, by hand
- Create or select a customer-managed KMS key with an appropriate key policy.
- Re-run the model customization job specifying the CMEK as the output model KMS key (existing custom models cannot be re-keyed in place).
- Validate the new model and cut traffic over to it.
- Delete the AWS-owned-key model once migration is confirmed.
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-1631- 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.