Skip to main content
Checks that AWS SQS message visibility timeout is being monitored.

​
About

When you connect Amazon Web Services (AWS) to DSALTA, the platform retrieves the list of resources in your environment using read-only API access. DSALTA then checks whether this configuration is in place. If it is not, DSALTA activates this check so you can remediate it.

​
Why This Matters

Infrastructure that is not monitored fails silently until it impacts users. Tracking key metrics — and alerting when they cross a threshold — lets you act before a small issue becomes an outage. Proactive monitoring is required by SOC 2 and ISO 27001.

​
How to Fix

Before you begin
  • Ensure you have Admin access to the AWS account to create CloudWatch alarms.
  • Confirm that you have Amazon SQS resources running for which you want to create the alarm.
Create the CloudWatch alarm
  1. Sign in to the AWS Management Console and navigate to CloudWatch.
  2. Go to Alarms → All alarms and click Create alarm.
  3. Click Select metric, choose the AWS/SQS namespace, and select the ApproximateNumberOfMessagesNotVisible metric for your resource.
  4. Set the condition to alert when the not-visible count grows persistently, then click Next.
  5. Under Notification, choose Create new topic (or select an existing SNS topic), enter the email addresses to receive alerts, and click Add notification.
  6. Click Next, enter a name and description for the alarm, then click Next again.
  7. Review the configuration and click Create alarm.
Once the CloudWatch alarm is configured for ApproximateNumberOfMessagesNotVisible, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Amazon Web Services (AWS) integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Amazon Web Services (AWS).