Bedrock Invocation Logging Disabled
There is no record of what was sent to or returned by the model, so misuse, cost spikes and data leaks cannot be investigated after the fact.
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: Enable Bedrock invocation logging.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Bedrock Provisioned Throughput on AWS
- The fix, by hand
- Decide the destination: CloudWatch Logs (easier search) or S3 (cheaper bulk retention).
- Bedrock → Settings → Model invocation logging → Edit → enable → pick destination.
- (Optional) configure separate request / response data sinks if you must split for compliance reasons.
- Set retention on the destination (CWL log group retention, or S3 lifecycle).
- Trigger a test InvokeModel call and confirm a log entry lands within 5 min.
These are the steps the finding carries in the product.
- Category
- Governance. Missing tags and labels that break cost attribution, such as no environment, team or cost-centre value.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1609- Full reference
Related checks
See the governance 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.