Skip to main content
Checks that AWS Elasticsearch cluster CPU utilization 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 administrator access to Amazon Web Services (AWS).
Remediate the configuration
  1. Review the failing configuration in your Amazon Web Services (AWS) console.
  2. Apply the recommended setting to bring the resource into compliance.
  3. Verify the change is active in the resource configuration.
Once the configuration is updated, 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).