Skip to main content

​
What this check does

Checks for listeners, target groups, and health checks. Passes when: All load balancers have valid configurations.

​
Why this matters

Valid configuration ensures load balancers function correctly.

​
How to fix

Fix the load balancer configuration
  1. Sign in to the AWS Console and navigate to EC2 → Load balancers.
  2. Select the failing load balancer and check the Details panel for warnings (state, Availability Zones, subnets).
  3. On the Listeners tab, confirm every listener has a valid protocol and port and a default action that forwards to an existing target group, and that HTTPS listeners have a valid SSL certificate.
  4. Under EC2 → Target groups, open each target group a listener forwards to, confirm it has registered targets, and review the Health checks tab (protocol, path, port, and healthy/unhealthy thresholds).
  5. Verify the load balancer’s Security groups allow inbound traffic on the listener ports and that at least two Availability Zones with valid subnets are enabled.
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.