Skip to main content
Checks that AWS load balancers redirect HTTP traffic to HTTPS.

​
About

When you connect Amazon Web Services (AWS) to DSALTA, the platform evaluates this control on every sync using read-only API access. If the requirement is not met, DSALTA activates this check.

​
Why This Matters

Traffic sent over plain HTTP can be intercepted or tampered with in transit. Enforcing HTTPS with a current TLS version protects data confidentiality and integrity and is a baseline requirement for PCI DSS, SOC 2, and GDPR.

​
How to Fix

Before you begin
  • Ensure you have Admin access to the AWS account.
  • Have a valid TLS certificate available in ACM.
Redirect HTTP to HTTPS on the load balancer
  1. Sign in to the AWS Console and navigate to EC2 → Load Balancers.
  2. Select the load balancer and open the Listeners tab.
  3. Edit the HTTP :80 listener and change its default action to Redirect to HTTPS :443 with status code 301.
  4. Ensure the HTTPS :443 listener has a valid certificate. Save changes.
Once HTTP redirects to HTTPS, 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).