An S3 bucket that is public means that anyone on the internet can access the contents of the bucket without any form of authentication or authorization. This can pose several risks, including: Data exposure: If the contents of the bucket are sensitive, such as personally identifiable information or confidential business data, then making it public can result in unauthorized access, theft, or disclosure of the data. Data tampering: If the bucket contains code or other executable content, then public access could enable an attacker to modify the code or replace it with their own malicious code, leading to compromise of the system or data. Resource exploitation: Public access to S3 buckets can also lead to resource exploitation, such as bandwidth or storage consumption, by unauthorized third parties or automated bots. Compliance violations: Depending on the type of data stored in the bucket, making it public may violate regulatory or contractual obligations, such as those under the GDPR or PCI DSS. It is essential to ensure that S3 buckets are not public and only accessible to authorized users to prevent these risks.


When an S3 bucket is public, it means that anyone on the internet can access and download its contents. This is a significant security risk as sensitive or confidential data stored in the bucket can be compromised. To remediate the issue, you can take the following steps:

  1. Access the AWS S3 Console and identify the public bucket.
  2. Update the bucket policy to deny public access.
  3. Remove public access to individual objects in the bucket, if required. This can be done by updating the object ACLs to remove "Everyone" or "All Users" from the list of users/groups with access to the object.
  4. Review your AWS Identity and Access Management (IAM) policies to ensure that they restrict access to S3 buckets and objects.
  5. Monitor S3 bucket policies to prevent future public access to the bucket. You can use AWS Config to monitor S3 bucket policies and receive alerts when there are changes to the policy.
Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.