Skip to main content
Checks that AWS S3 bucket versioning is enabled.

​
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

Without versioning, a single overwrite or deletion is permanent. Keeping prior versions protects against accidental loss and tampering and supports recovery requirements in SOC 2 and ISO 27001.

​
How to Fix

Before you begin
  • Ensure you have Admin access to the AWS account.
Enable S3 bucket versioning
  1. Sign in to the AWS Console and navigate to S3 → Buckets.
  2. Select the bucket and open the Properties tab.
  3. Under Bucket Versioning, click Edit, choose Enable, and save.
  4. (Optional) Add a lifecycle rule to expire or transition old versions.
Once versioning 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).