DynamoDB throttling

Turbot relies heavily on DynamoDB, with tables such as TurbotGuardRails, TurbotUsers, and TurbotStacks. With improper read and write capacity in these various tables, it can lead to slow searches, control runs taking longer than normal to complete, and other issues related to Turbot being unable to read and write data to a specific table.

To fix this issue, first you must be able to log into the Turbot master account in AWS. Search for DynamoDB and navigate to tables on the left side. Select the table that most reasonably matches with the issue you are seeing and click on the metrics tab. Here, the graphs can show when the read and/ or write capacity of the table was maxed out, and the provisioned IOPS can be adjusted to better fit the actual data.

Some tables to check are:

  • TurbotGuardrails
  • TurbotNotifications
  • TurbotOptionSetting
  • TubotStacks

Be sure to look at the following time scales: 1, 3, 6 hours, 1 day, and past week to determine if there are any outliers that can be ignored. Make changes to the affected tables, save the configuration, and wait approximately 5 minutes for the IOPS adjustments to take effect.

As environments grow, it is important to keep an eye on these tables to ensure proper function.

AWS introduced DynamoDB On-Demand provisioning in November of 2018. Turning this feature on allows admins to avoid having to look at read or write capacity and instead focus on other areas. This feature will be the default setting in future releases, and currently Turbot recommends that On-Demand be enabled for each table within DynamoDB.

Please reach out to Turbot support at help@turbot.com if issues persist.

Was this article helpful?
0 out of 0 found this helpful