S3 Bucket Not Requiring HTTPS
Objects can be fetched over plain HTTP, exposing their contents and the request's credentials in transit.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Enforce HTTPS-only access on S3 bucket.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- S3 Buckets on AWS
- The fix, by hand
- S3 → bucket the resource → Permissions → Bucket policy → Edit.
- Add a Deny statement on Action s3:* / Resource the bucket + /* / Condition aws:SecureTransport = false.
- Save and verify an HTTP curl returns 403 (HTTPS must still succeed).
- Repeat across every bucket. Use a Service Control Policy at the Organization level to enforce account-wide.
- Add an alerting rule on CloudTrail aws:SecureTransport=false events to catch regressions.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1524- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.