Error: DynamoDB Auto Scaling Not Working
What's Causing This Error
After turning on auto-scaling, you may encounter situations where your read/write activities get throttled, and the scaling does not work as initially intended. This might happen when your work is not staying elevated for a long time. The provisional throughput is modified by DynamoDB auto-scaling only when the workload remains elevated or depressed for a few minutes.
Solution: Here's How To Resolve It
DynamoDB auto scaling creates CloudWatch alarms to trigger auto-scaling. So, ensure that you do not delete any of these alarms. If you delete them, auto-scaling will not function as you expect. If you accidentally deleted these alarms, you can disable and enable auto-scaling once again, which will recreate the CloudWatch alarms.
However, suppose your elevation or depression of workload is limited to a short time. In that case, auto-scaling will not work properly as it is not the best in handling short-duration activity spikes.
You can read more about auto-scaling issues and their resolution here.
Other Common DynamoDB Errors (with Solutions)
- dynamodb throttle error code
- DynamoDB Is Not Null
- dynamodb list_append returns true but does not work
- dynamodb query key condition not supported
- ValidationException: Invalid KeyConditionExpression: Attribute name is a reserved keyword;
- dynamodb query not returning the full item
- comparison operator does not return all attributes dynamodb
- ExpressionAttributeValues contains invalid value: One or more parameter values were invalid: An AttributeValue may not contain an empty string
- aws.dynamodb.converter.unmarshall not working
- ProvisionedThroughputExceededException DynamoDB
- Float types are not supported. Use decimal types instead.
- dynamodb local shell not working
- dynamodb ttl not deleting / erasing items
- dynamodb list_append if_not_exists not working
- DynamoDB Network Error: self signed certificate in chain