DynamoDB Auto Scaling Disabled
Capacity is fixed, so traffic above it is throttled and rejected while capacity below it is paid for regardless.
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 auto scaling on DynamoDB table.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- DynamoDB Tables on AWS
- The fix, by hand
- Open DynamoDB → Tables → select → Additional settings → Capacity.
- Choose Auto scaling: set target utilisation to 70% as a starting point.
- Set min/max capacity bounds (size to comfortably cover peak + ~30% headroom).
- Apply (online; no table lock).
- Validate ConsumedReadCapacityUnits / WriteCapacityUnits track the target after one full traffic cycle.
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-1515- 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.