3 ms·
How about monitoring via polling? I'm imagining something like this... - Set up application with your AWS/S3 credentials - Poll S3 to get list of all your bu
by amorphid 9y ago
How about monitoring via polling? I'm imagining something like this...
- Set up application with your AWS/S3 credentials
- Poll S3 to get list of all your buckets on a regular interval (once a day, every 5 minutes, whatever)
- Get a list of some files in those buckets
- Try to access those files directly w/ no authentication or authorization
- Set up some rules about how to interpret the results (look for any public files, look for specific private buckets, look any buckets that are public & haven't been whitelisted, whatever)
There's probably a ton of ways to do this. For simple use cases, it shouldn't be too tough. That'd be a fun hack for a day project, and I'd be happy to pair with you on it if interested. It's probably spending a little time looking around for an off the shelf solution first.
- cortesoft 9y agoA private bucket isn’t going to turn itself public on accident. This error wasn’t the bucket suddenly becoming public, it was a developer making it public because that was the easiest way to get the job done. Your testing system would not help here at all, and if you spent the effort to make the system, you are already the type of person who isn’t going to turn the bucket public to make your life easier.