> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AWS RDS database storage should be encrypted

> Checks that AWS RDS database storage is encrypted at rest.

Checks that AWS RDS database storage is 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.
* Note: encryption at rest can only be enabled when an RDS instance is created. Existing unencrypted instances must be migrated via an encrypted snapshot.

**Encrypt the RDS database**

1. Sign in to the [AWS Console](https://console.aws.amazon.com/) and navigate to **RDS → Databases**.
2. Select the unencrypted instance and choose **Actions → Take snapshot**.
3. Select the new snapshot, then choose **Actions → Copy snapshot**.
4. Under **Encryption**, enable **Enable encryption** and select your KMS key. Create the copy.
5. Select the encrypted snapshot and choose **Actions → Restore snapshot** to launch a new, encrypted instance.
6. Repoint your application to the encrypted instance and retire the old one.

Once the database storage is encrypted, DSALTA retrieves the change on the next sync and sets the check status to **Passing**.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How often does this check run?">
    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.
  </Accordion>

  <Accordion title="What happens if it keeps failing?">
    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.
  </Accordion>

  <Accordion title="Can I exclude this check?">
    Yes. If it does not apply to your environment, mark it as **Not Applicable** with a justification. The exclusion is documented for auditors.
  </Accordion>

  <Accordion title="Does DSALTA change my Amazon Web Services (AWS) configuration?">
    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).
  </Accordion>
</AccordionGroup>