How to Fix the Error AccessControlListNotSupported while Deploying an Amazon S3 Bucket from GitHub

As a data scientist or software engineer, deploying an Amazon S3 bucket from GitHub is a common task that you might encounter. However, one of the most common errors that you might encounter during this process is the AccessControlListNotSupported error. This error indicates that the bucket does not allow Access Control Lists ACLs which are used to manage access to your S3 bucket. In this article, we will discuss how to fix this error and successfully deploy your S3 bucket from GitHub.

Table of Contents

  1. What is an Access Control List (ACL)?
  2. How to Fix the AccessControlListNotSupported Error
  1. Best Practice
  2. Conclusion

What is an Access Control List (ACL)?

Before we dive into the solution, it’s important to understand what an Access Control List (ACL) is. An ACL is a set of rules that define who can access an S3 bucket and what level of access they have. There are two types of ACLs in S3:

  • Bucket ACLs: These define the permissions for the bucket itself, such as who can list the contents of the bucket or delete objects from it.
  • Object ACLs: These define the permissions for individual objects within the bucket, such as who can read, write, or delete the object.

When deploying an S3 bucket from GitHub, you may encounter the AccessControlListNotSupported error if the bucket does not support ACLs.

How to Fix the AccessControlListNotSupported Error

There are a few steps you can take to fix the AccessControlListNotSupported error and successfully deploy your S3 bucket from GitHub.

Step 1: Check the Bucket’s Permissions

The first step is to check the permissions of the S3 bucket that you want to deploy from GitHub. You can do this by logging into the AWS Management Console and navigating to the S3 service. From there, click on the name of the bucket that you want to deploy from GitHub.

Once you are on the bucket’s overview page, click on the “Permissions” tab. From there, you can check if the bucket has ACLs enabled or disabled. If ACLs are disabled, you will need to enable them before you can deploy from GitHub.

Step 2: Enable ACLs on the Bucket

If ACLs are disabled on the bucket, you can enable them by following these steps:

  1. Click on the “Edit bucket policy” button in the “Permissions” tab of the bucket’s overview page.
  2. In the bucket policy editor, add the following policy to enable ACLs:
  "Version": "2012-10-17",
  "Statement": [
      "Sid": "Enable ACLs",
      "Effect": "Allow",
      "Principal": "*",
      "Action": [
      "Resource": "arn:aws:s3:::your-bucket-name"

Make sure to replace “your-bucket-name” with the name of your S3 bucket.

  1. Save the bucket policy by clicking on the “Save changes” button.

Step 3: Deploy the S3 Bucket from GitHub

Once you have enabled ACLs on the S3 bucket, you can now deploy the bucket from GitHub without encountering the AccessControlListNotSupported error. Here are the steps to do so:

  1. In your GitHub repository, navigate to the “Actions” tab.
  2. Click on the “New workflow” button and select “Set up a workflow yourself”.
  3. In the workflow editor, add the following code to deploy the S3 bucket:
name: Deploy S3 Bucket

      - main

    runs-on: ubuntu-latest
    - name: Checkout repository
      uses: actions/checkout@v2
    - name: Configure AWS credentials
      uses: aws-actions/configure-aws-credentials@v1
        aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
        aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
        aws-region: us-east-1
    - name: Deploy to S3
      run: |
        aws s3 sync . s3://your-bucket-name --delete --acl public-read
  1. Make sure to replace “your-bucket-name” with the name of your S3 bucket.
  2. Save the workflow by clicking on the “Start commit” button.

With these steps, you should now be able to deploy your S3 bucket from GitHub without encountering the AccessControlListNotSupported error.

Best Practice

While fixing the AccessControlListNotSupported error allows you to deploy your S3 bucket, let’s dive deeper into best practices for secure and efficient deployments from GitHub:


  • Granular Access Control: Public-read access, while convenient, might not be suitable for sensitive data. Explore IAM policies for fine-grained control over object permissions for different users and groups.

  • Secure Credentials Management: Avoid hardcoding credentials in your workflow. Use environment variables stored securely in GitHub Secrets or leverage AWS IAM roles for temporary access.

  • Logging and Auditing: Enable S3 bucket logging to track changes and potential security breaches. Analyze logs regularly for suspicious activity.


  • Automation: Consider tools like AWS CloudFormation or Terraform for deploying infrastructure and S3 buckets as code. This enables automation, repeatability, and version control.

  • Environment Variables: Use environment variables to configure region, bucket names, and other details. This allows easy adaptation and deployment to different environments.

Error Handling and Recovery:

  • Graceful Error Handling: Implement error handling mechanisms in your deployment script to handle unexpected situations like missing files or permissions issues.

  • Informative Logging: Log errors with clear messages and context for easier debugging and troubleshooting. Consider using tools like CloudWatch for centralized logging.

  • Rollback Strategies: Plan for rollbacks in case of deployment failures. Utilize S3 versioning to revert to previous states if needed.

By following these best practices, you can ensure your S3 deployments from GitHub are secure, efficient, and well-prepared for potential challenges. Remember, cloud infrastructure is a powerful tool, so use it responsibly and strategically for optimal results.


Deploying an Amazon S3 bucket from GitHub is a common task for data scientists and software engineers. However, it’s important to understand the role of Access Control Lists (ACLs) in managing access to your S3 bucket. If you encounter the AccessControlListNotSupported error while deploying your S3 bucket from GitHub, follow the steps outlined in this article to enable ACLs on your bucket and successfully deploy your bucket.

About Saturn Cloud

Saturn Cloud is your all-in-one solution for data science & ML development, deployment, and data pipelines in the cloud. Spin up a notebook with 4TB of RAM, add a GPU, connect to a distributed cluster of workers, and more. Request a demo today to learn more.