Require HTTPS for access to resources
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Require HTTPS for access to resources is an AWS guardrail written in resource control policies. Denies requests to resources in the listed services (S3, STS, KMS, SQS, Secrets Manager, Cognito, CloudWatch Logs, DynamoDB, ECR, OpenSearch Serverless) when aws:SecureTransport is false.
More encryption and keys guardrails ยท About Resource control policies
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Deny",
"Principal": "*",
"Action": [
"s3:*",
"sts:*",
"kms:*",
"sqs:*",
"secretsmanager:*",
"cognito-identity:*",
"cognito-idp:*",
"logs:*",
"dynamodb:*",
"ecr:*",
"aoss:*"
],
"Resource": "*",
"Condition": {
"BoolIfExists": {
"aws:SecureTransport": "false"
}
}
}
]
}
- Blocks
- Denies requests to resources in the listed services (S3, STS, KMS, SQS, Secrets Manager, Cognito, CloudWatch Logs, DynamoDB, ECR, OpenSearch Serverless) when aws:SecureTransport is false.
- Breaks
- Callers outside the organization, including trusted partners, are also denied if they connect over an unencrypted connection, because RCPs apply regardless of whether the principal belongs to the organization. (source)
- Test before applying
- As for every Resource control policies guardrail: how to test before enforcing
- Mechanism
- Resource control policies (RCPs): Resources of supported services in member accounts, for any principal calling them; not resources in the management account and not service-linked roles.
- Taken from
- open source set, MIT-0 (README states MIT-0; LICENSE file fetched, MIT-0 text, Copyright Amazon.com, Inc.): https://raw.githubusercontent.com/aws-samples/resource-control-policy-examples/main/LICENSE
What the policy text names
It names 11 actions or patterns: s3:*, sts:*, kms:*, sqs:*, secretsmanager:*, cognito-identity:*, cognito-idp:*, logs:*, and more. Its conditions test aws:SecureTransport.
What the source says
"aws:SecureTransport: false" (read 10 Nov 2026).
On what it breaks: "This can help you prevent potential attackers from manipulating network traffic and trusted partners from accessing your resources over an unencrypted connection."
Related guardrails
- Storage accounts should have the specified minimum TLS versionAzure, Azure Policy (built-in definitions), encryption and keys
- Key vaults should have deletion protection enabledAzure, Azure Policy (built-in definitions), encryption and keys
- OS and data disks should be encrypted with a customer-managed keyAzure, Azure Policy (built-in definitions), encryption and keys
- Deny KMS key deletionAWS, Service control policies (SCPs), encryption and keys
- Enforce a 30-day KMS key deletion windowAWS, Service control policies (SCPs), encryption and keys
- Deny disabling default EBS encryptionAWS, Service control policies (SCPs), encryption and keys
Related pages
Sources
- Require HTTPS for access to resources, read 10 Nov 2026
- What it breaks, read 10 Nov 2026
- How to test it first, read 10 Nov 2026
Last reviewed 16 Nov 2026.