Skip to main content

​
What this check does

Checks for CloudWatch alarms on SuccessfulRequestLatency. Passes when: All DynamoDB tables have latency monitoring.

​
Why this matters

Latency monitoring detects performance degradation.

​
How to fix

Create a CloudWatch alarm for DynamoDB request latency
  1. Sign in to the AWS Console and navigate to CloudWatch → Alarms → Create alarm.
  2. Click Select metric, open the DynamoDB → Table Operation Metrics namespace, and select SuccessfulRequestLatency for the affected table and operation (e.g., Query or PutItem).
  3. Set the condition to trigger when average latency exceeds 20 ms for reads or 50 ms for writes, adjusted to your workload.
  4. Under Notification, select or create an SNS topic that delivers alerts to your team (email, Slack, or PagerDuty).
  5. Name the alarm descriptively (e.g., dynamodb-latency-high) and click Create alarm.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.