S3 bucket policies should deny requests made over plain HTTP
This check looks at each S3 bucket policy for a statement that denies requests made without TLS. The safe setting is a Deny on requests where aws:SecureTransport is false, so data only travels over HTTPS.
Why it matters
Without a rule, S3 will answer a request sent over plain HTTP, and anything sent that way can be read or altered by someone on the network path. AWS recommends allowing only encrypted connections by using the aws:SecureTransport condition in bucket policies.
AWS also suggests a CloudWatch alarm on HTTP access attempts, and the AWS Config managed rule s3-bucket-ssl-requests-only as an ongoing detective control.
Source: Amazon S3 User Guide, Security best practices for Amazon S3.
How to check it yourself
Console: S3 > select the bucket > Permissions > Bucket policy, and look for a Deny statement with the condition aws:SecureTransport set to false. Read-only commands:
aws s3api list-buckets --query "Buckets[].Name" --output text
aws s3api get-bucket-policy --bucket --query Policy --output text A bucket with no policy, or a policy without that statement, is a finding.
How to fix it
Add a statement like the one below to each bucket policy, merging it with any existing statements instead of replacing them. Console: bucket > Permissions > Bucket policy > Edit.
{
"Sid": "DenyInsecureTransport",
"Effect": "Deny",
"Principal": "*",
"Action": "s3:*",
"Resource": ["arn:aws:s3:::", "arn:aws:s3:::/*"],
"Condition": {"Bool": {"aws:SecureTransport": "false"}}
} Apply it with aws s3api put-bucket-policy after fetching and editing the current policy. ConfigCobra itself never changes your AWS account; it reports the finding and suggests these steps. Test on a non-production bucket first.
What changes when you fix it
Any client, script or application still calling the bucket over HTTP starts receiving access denied errors, so find those first, for instance in server access logs or CloudTrail data events. Most modern SDKs and the AWS CLI already use HTTPS, so older tools, hard-coded endpoints and some third-party integrations are the likely casualties. Static website endpoints serve HTTP only, so a bucket used that way would break if the rule applies to it. Application owners and anyone with scheduled transfers are the people to warn.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Amazon Web Services Foundations v7.0.0 | 3.1.1 | Level 2 |
Check this on your AWS
ConfigCobra runs this check with every other control of the CIS Amazon Web Services Benchmarks, read-only.