Skip to main content
Checks that AWS S3 buckets are encrypted at rest.

​
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

Data stored without encryption can be read by anyone who gains access to the underlying storage — through a misconfiguration, a stolen disk, or improper decommissioning. Encryption at rest renders that data useless without the key and is required by SOC 2, ISO 27001, HIPAA, and PCI DSS.

​
How to Fix

Before you begin
  • Ensure you have Admin access to the AWS account.
Enable default encryption on the S3 bucket
  1. Sign in to the AWS Console and navigate to S3 → Buckets.
  2. Select the bucket and open the Properties tab.
  3. Under Default encryption, click Edit.
  4. Choose Server-side encryption with Amazon S3 managed keys (SSE-S3) or with AWS KMS keys (SSE-KMS).
  5. Click Save changes.
Once default encryption is enabled, 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).