Auto-Scale DynamoDB Read and Write Capacity
Enable autoscaling on the table with a target utilization of 70 percent so a traffic spike does not throttle reads or writes.
Task
Configure aws applicationautoscaling register-scalable-target --service-namespace dynamodb --resource-id table/Events --scalable-dimension dynamodb:table:ReadCapacityUnits --min-capacity 5 --max-capacity 100 so the cloud resource enforces the control automatically without manual console steps.
When to use this
An audit finds that aws applicationautoscaling register-scalable-target --service-namespace dynamodb --resource-id table/Events --scalable-dimension dynamodb:table:ReadCapacityUnits --min-capacity 5 --max-capacity 100 was configured manually and drifted, leaving a resource exposed for two weeks.
Prerequisites
- Terraform or IaC tooling installed
- Cloud provider credentials with target permissions
Steps
1. Configure aws applicationautoscaling register-scalable-target --service-namespace dynamodb --resource-id table/Events --scalable-dimension dynamodb:table:ReadCapacityUnits --min-capacity 5 --max-capacity 100 in the project configuration file with the recommended defaults.
aws applicationautoscaling register-scalable-target --service-namespace dynamodb --resource-id table/Events --scalable-dimension dynamodb:table:ReadCapacityUnits --min-capacity 5 --max-capacity 100
Expected output: The configuration is accepted and aws applicationautoscaling register-scalable-target --service-namespace dynamodb --resource-id table/Events --scalable-dimension dynamodb:table:ReadCapacityUnits --min-capacity 5 --max-capacity 100 runs without errors on the first invocation.
2. Run the check locally to verify aws applicationautoscaling register-scalable-target --service-namespace dynamodb --resource-id table/Events --scalable-dimension dynamodb:table:ReadCapacityUnits --min-capacity 5 --max-capacity 100 produces the expected result before pushing.
pnpm test
Expected output: Local run matches CI behavior; no surprises after push.
3. Add the gate to the CI pipeline so aws applicationautoscaling register-scalable-target --service-namespace dynamodb --resource-id table/Events --scalable-dimension dynamodb:table:ReadCapacityUnits --min-capacity 5 --max-capacity 100 blocks merge on failure.
- name: Run add dynamodb autoscaling
run: pnpm test
Expected output: Pull requests with failing aws applicationautoscaling register-scalable-target --service-namespace dynamodb --resource-id table/Events --scalable-dimension dynamodb:table:ReadCapacityUnits --min-capacity 5 --max-capacity 100 are blocked from merging.
Troubleshooting
Problem
The check passes locally but fails in CI
Solution
Pin dependency versions and the runtime to match CI exactly; reproduce with the same Docker image or act.
Problem
Configuration is rejected with a schema error
Solution
Check the tool version matches the config schema; older versions may not support newer fields.
Limitations
- The gate only runs on events that trigger the workflow; locally pushed commits bypass it.
- Configuration drift is possible if someone edits settings outside version control.
Codify the control
Start by measuring the problem. Enable autoscaling on the table with a target utilization of 70 percent so a traffic spike does not throttle reads or writes. The most common mistake is adding the gate without first confirming it catches the issue you care about. Run aws applicationautoscaling register-scalable-target –service-namespace dynamodb –resource-id table/Events –scalable-dimension dynamodb:table:ReadCapacityUnits –min-capacity 5 –max-capacity 100 against the current codebase and inspect the output before wiring it into CI.
aws applicationautoscaling register-scalable-target --service-namespace dynamodb --resource-id table/Events --scalable-dimension dynamodb:table:ReadCapacityUnits --min-capacity 5 --max-capacity 100Detect drift
Once the gate is in place, make failures actionable. A failing aws applicationautoscaling register-scalable-target –service-namespace dynamodb –resource-id table/Events –scalable-dimension dynamodb:table:ReadCapacityUnits –min-capacity 5 –max-capacity 100 should point to the exact file and line, not a generic error. Pin the tool version in the lockfile so a upstream release does not silently change behavior. Review the gate output in every pull request just like a test result.