# Ensure Block Public Access Settings enabled on Multi-Region Access Points

- Source: https://support.icompaas.com/support/solutions/articles/62000233387-ensure-block-public-access-settings-enabled-on-multi-region-access-points
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS Checks New Version](https://support.icompaas.com/support/solutions/62000112673) › [AWS New Checks](https://support.icompaas.com/support/solutions/folders/62000169206)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Profile Applicability:**  

-   **Level 2**

**Description:**  
Amazon S3 Multi-Region Access Points provide a global routing mechanism for S3 requests, enabling seamless data access across multiple regions. These access points allow users to access S3 data in different AWS regions through a single endpoint. However, to maintain a secure environment, it is important to ensure that Block Public Access Settings are enabled on Multi-Region Access Points. This ensures that no public access can be granted to the resources managed through the Multi-Region Access Points, thus reducing the risk of accidental exposure of sensitive data.

**Rationale:**  
Enabling the Block Public Access Settings ensures that no unintended public access can be granted to S3 buckets or objects accessible through Multi-Region Access Points. This helps prevent the accidental exposure of sensitive data, ensuring that only authorized users and applications have access to the data. Public access to Multi-Region Access Points could lead to security vulnerabilities, data breaches, or non-compliance with regulatory requirements.

**Impact:  
 Pros:**

-   Prevents accidental public access to data managed by Multi-Region Access Points.
    
-   Enhances the security of S3 data by ensuring only authorized access.
    
-   Helps comply with data protection regulations such as GDPR, HIPAA, and SOC 2.
    
-   Ensures proper access controls are in place for all regions, preventing inconsistent security settings.
    

**Cons:**

-   May require additional configuration and management if public access is needed for specific use cases.
    
-   Could complicate access control management if public access is needed for legitimate purposes, requiring the use of signed URLs or other access mechanisms.
    

**Default Value:**  
By default, Multi-Region Access Points do not have Block Public Access Settings enabled. These settings must be explicitly configured to block all public access.

**Pre-requisites:**

-   AWS IAM permissions to configure Multi-Region Access Points and public access settings:  
    s3control:PutMultiRegionAccessPoint  
     s3control:GetMultiRegionAccessPoint
    
-   Access to configure the Multi-Region Access Point settings.
    

**Remediation:**

**Test Plan:**

**Using AWS Console :**

1.  Sign in to the AWS Management Console.
    
2.  Navigate to S3 and select Multi-Region Access Points from the left-hand menu.
    
3.  Select the Multi-Region Access Point you want to check.
    
4.  Under the Block Public Access settings section, verify if the following options are enabled:
    
    -   Block all public access to this access point and its resources
        
    -   Block public access from any public policies
        
    -   Block public access from any access control lists (ACLs)
        
5.  If these settings are not enabled, click Edit, enable the required public access block settings, and save the changes.
    

**Using AWS CLI :**

1.  List all Multi-Region Access Points:  
    
    aws s3control list-multi-region-access-points --account-id <ACCOUNT\_ID>
    
2.  For each Multi-Region Access Point, check the current Block Public Access settings:  
    
    aws s3control get-multi-region-access-point --account-id <ACCOUNT\_ID> --name <ACCESS\_POINT\_NAME>
    
3.  If Block Public Access settings are not enabled, run the following command to enable them:  
    
    aws s3control put-multi-region-access-point --account-id <ACCOUNT\_ID> --name <ACCESS\_POINT\_NAME> --block-public-access "BlockPublicAcls=true,IgnorePublicAcls=true,BlockPublicPolicy=true,RestrictPublicBuckets=true"
    
4.  Verify the settings are updated:  
    
    aws s3control get-multi-region-access-point --account-id <ACCOUNT\_ID> --name <ACCESS\_POINT\_NAME>
    

**Implementation Plan:**

**Using AWS Console :**

1.  Open the S3 Console and select Multi-Region Access Points.  
    ![](https://support.icompaas.com/assets/kb/42bc74e5dd3f866d.png)  
    ![](https://support.icompaas.com/assets/kb/17bdec96446f2ebe.png)
    
2.  Choose the Multi-Region Access Point you want to configure.  
    ![](https://support.icompaas.com/assets/kb/2edbd413a6ed074f.png)
    
3.  Under Block Public Access, enable the settings to block all public access and restrict public access to any resources managed through the access point.  
    ![](https://support.icompaas.com/assets/kb/cd9157a685f03c7e.png)  
    ![](https://support.icompaas.com/assets/kb/2059e23e4e5dbc6f.png)
    
4.  Save the changes and verify that public access is now blocked for the Multi-Region Access Point.
    

**Using AWS CLI:**

1.  Run the following command to enable Block Public Access settings:  
    
    aws s3control put-multi-region-access-point --account-id <ACCOUNT\_ID> --name <ACCESS\_POINT\_NAME> --block-public-access "BlockPublicAcls=true,IgnorePublicAcls=true,BlockPublicPolicy=true,RestrictPublicBuckets=true"
    
2.  Verify the changes by running:  
    
    aws s3control get-multi-region-access-point --account-id <ACCOUNT\_ID> --name <ACCESS\_POINT\_NAME>
    

**Backout Plan:** 

**Using AWS Console:**

1.  If blocking public access causes issues, sign in to the AWS Management Console.
    
2.  Navigate to Amazon S3 and select the Multi-Region Access Point.  
       ![](https://support.icompaas.com/assets/kb/415198f9adeef987.png) ![](https://support.icompaas.com/assets/kb/fc7f5938d073a5cc.png) ![](https://support.icompaas.com/assets/kb/de9084a559c23fb7.png)
    
3.  Click Edit and disable Block Public Access Settings to allow public access if required.  
    ![](https://support.icompaas.com/assets/kb/f9ffcb8207ce6142.png)  
    ![](https://support.icompaas.com/assets/kb/0665c8cc569fe540.png)
    
4.  Save the changes and monitor the access point to ensure it functions as expected.
    

**Using AWS CLI:**

1.  To disable Block Public Access Settings, run:  
    
    aws s3control put-public-access-block --account-id <ACCOUNT\_ID> --bucket <MULTI\_REGION\_ACCESS\_POINT\_NAME> --public-access-block-configuration '{
    
      "BlockPublicAcls": false,
      "IgnorePublicAcls": false,
      "BlockPublicPolicy": false,
      "RestrictPublicBuckets": false
    
    }'
    

2.  Verify that public access is now allowed:  
    
    aws s3control get-public-access-block --account-id <ACCOUNT\_ID> --bucket <MULTI\_REGION\_ACCESS\_POINT\_NAME>
    

**Reference:**

-   [Amazon S3: Multi-Region Access Points](https://docs.aws.amazon.com/AmazonS3/latest/userguide/multi-region-access-points.html)
    
-   [AWS CLI: list-multi-region-access-points](https://docs.aws.amazon.com/cli/latest/reference/s3control/list-multi-region-access-points.html)
    
-   [AWS CLI: put-multi-region-access-point](https://docs.aws.amazon.com/cli/latest/reference/s3control/put-multi-region-access-point.html)
    
-   [AWS CLI: get-multi-region-access-point](https://docs.aws.amazon.com/cli/latest/reference/s3control/get-multi-region-access-point.html)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
