Someone accidentally made a bucket public
First minutes: contain. Then scope. Then notify.
Try this first
- 1Enable Block Public Access on the bucket and account immediately
- 2Check S3 access logs and CloudTrail for download activity
- 3Determine what was in the bucket, processors, and whose data is affected
- 4Document the timeline for the incident report
When to bring us in
For personal data: GDPR notification to DPA within 72 hours if risk to data subjects.
See also
- Everyone logs in with the AWS root accountRoot is for emergencies and billing. Day-to-day work belongs in IAM users or SSO.
- Every developer has AdministratorAccessAdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.