> ## 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 S3 bucket public access should be blocked

> Checks that AWS S3 bucket public access block is enabled.

Checks that AWS S3 bucket public access block 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

Resources reachable directly from the internet are constantly scanned and probed for weaknesses. Removing public exposure and placing resources behind private networks or tight firewall rules dramatically shrinks your attack surface — a fundamental control in SOC 2, ISO 27001, and PCI DSS.

## How to Fix

**Before you begin**

* Ensure you have **Admin** access to the AWS account.
* Verify your applications do not rely on public bucket access before enabling the block.

**Block public access on the S3 bucket**

1. Sign in to the [AWS Console](https://console.aws.amazon.com/) and navigate to **S3 → Buckets**.
2. Select the bucket and open the **Permissions** tab.
3. Under **Block public access (bucket settings)**, click **Edit**.
4. Enable **Block all public access** (all four settings) and click **Save changes**, then confirm.
5. To enforce account-wide, repeat under **S3 → Block Public Access settings for this account**.

Once public access is blocked, 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>