Study guide

7.4 Enforcing Encryption in Transit: ELB Security Policies, TLS & HTTPS-Only Access

AWS Certified Security – Specialty SCS-C03

Track your progress as you read

Finished sections get a check mark.

1 Chapter 0: Getting Started with the SCS-C03 Exam

0.1 SCS-C03 Exam Format, Domains & Study Strategy

2 Chapter 1: Security Monitoring, Alerting & Threat Detection Services

1.1 Workload Monitoring & Health Check Strategies 1.2 Amazon GuardDuty Architecture & Finding Types 1.3 AWS Security Hub & Automated Conformance Assessment 1.4 Amazon Macie & Automated Data Classification

3 Chapter 2: Enterprise Logging Architecture & Analysis

2.1 Multi-Account CloudTrail & Organization Trails 2.2 Amazon Security Lake & OCSF Log Normalization 2.3 Network Telemetry: VPC Flow Logs & Route 53 Resolver Logs 2.4 Troubleshooting Security Telemetry & Log Ingestion 2.5 Analyzing, Normalizing & Correlating Security Logs

4 Chapter 3: Incident Readiness, Response Planning & Automated Runbooks

3.1 Incident Response Planning & Blast Radius Mitigation 3.2 Testing & Validating Incident Response Plans 3.3 Automated Incident Remediation with EventBridge & Step Functions 3.4 Systems Manager OpsCenter & Incident Manager Runbooks

5 Chapter 4: Digital Forensics, Evidence Preservation & Root Cause Analysis

4.1 Forensic Artifact Capture & Chain of Custody 4.2 Threat Containment & Network Quarantine Techniques 4.3 Correlating Events & Root Cause Analysis with Amazon Detective

6 Chapter 5: Edge Protection, WAF & DDoS Mitigation

5.1 CloudFront Security Headers & Origin Access Control 5.2 AWS WAF Architecture & Advanced Rule Sets 5.3 AWS Shield Advanced & DDoS Defense Architectures 5.4 Edge Integrations: Managed Rule Groups, OCSF Ingestion, IoT Policies & CORS

7 Chapter 6: Compute Workload Hardening, Vulnerability Management & GenAI Security

6.1 Golden AMIs & Container Image Hardening Pipelines 6.2 Amazon Inspector Vulnerability Management & Patch Automation 6.3 Generative AI Security: Amazon Bedrock Guardrails & Model Protection 6.4 Instance Profiles, Service Roles & Execution Roles for Compute 6.5 Secure Administrative Access: Session Manager & EC2 Instance Connect

8 Chapter 7: Network Security, Segmentation, Private Connectivity & Encryption in Transit

7.1 Layered Traffic Filtering: SGs, NACLs & AWS Network Firewall 7.2 Hybrid Connectivity Security: VPN, Direct Connect & MACsec 7.3 Zero-Trust Access & Network Access Analysis 7.4 Enforcing Encryption in Transit: ELB Security Policies, TLS & HTTPS-Only Access 7.5 Private Access: VPC Endpoints, PrivateLink, Client VPN & Verified Access 7.6 Inter-Resource Encryption in Transit: Nitro, EMR, EKS & SageMaker AI

9 Chapter 8: Enterprise Authentication, Federation & Directory Services

8.1 AWS IAM Identity Center & Enterprise IdP Integration 8.2 Amazon Cognito User Pools & Identity Pools 8.3 AWS Security Token Service (STS) & Temporary Credential Workflows 8.4 Troubleshooting Identity & Authentication Failures

10 Chapter 9: Advanced Authorization Architecture & Policy Evaluation

9.1 Complete AWS Policy Evaluation Logic & Decision Flow 9.2 Permission Boundaries & Safe Admin Delegation 9.3 Attribute-Based Access Control (ABAC) with IAM Tags

11 Chapter 10: Least Privilege, Policy Validation & External Access Auditing

10.1 IAM Roles Anywhere & Amazon Verified Permissions 10.2 Auditing External & Unused Access with IAM Access Analyzer 10.3 Analyzing Authorization Failures & Policy Simulation

12 Chapter 11: Cryptographic Services: KMS Architecture & Key Governance

11.1 AWS KMS Architecture, Key Policies & Key Types 11.2 KMS Grants, Encryption Context & Multi-Region Keys 11.3 Imported Key Material (BYOK) & CloudHSM Key Stores

13 Chapter 12: Secrets Management, Sensitive Data Masking & PKI

12.1 AWS Secrets Manager & Systems Manager Parameter Store 12.2 Sensitive Data Masking in Telemetry & Messaging 12.3 AWS Certificate Manager (ACM) & Private CA Architecture

14 Chapter 13: Storage Encryption, Integrity, Lifecycle & Backup Protection

13.1 S3 Encryption Modes & S3 Bucket Keys 13.2 Data Integrity Protection: Object Lock, Vault Lock & Code Signing 13.3 Secure Data Lifecycle, Cross-Account Replication & Backup Vault Lock 13.4 Lifecycle, Backup & Secure Replication Beyond S3: EFS, FSx, DLM, DataSync & Air-Gapped Vaults

15 Chapter 14: Multi-Account Architecture, Organizations & Control Tower Governance

14.1 AWS Organizations Structure, Hierarchy & Resource Control 14.2 AWS Control Tower Landing Zone & Guardrail Framework 14.3 Delegated Administrator Architecture & Root User Governance 14.4 Centralized Resource Sharing with RAM & Service Catalog

16 Chapter 15: Compliance Automation, Infrastructure as Code Security & Auditing

15.1 Infrastructure as Code Security & Multi-Account Deployment 15.2 AWS Config, Conformance Packs & Automated Remediation 15.3 Audit Evidence Collection & Well-Architected Security Reviews

7.4 Enforcing Encryption in Transit: ELB Security Policies, TLS & HTTPS-Only Access

Key Takeaways Explain This Topic AI

ALB HTTPS listeners should use an explicit security policy; the API default ELBSecurityPolicy-2016-08 still permits older TLS versions.

An HTTP listener that only redirects to HTTPS, plus HTTPS target groups, keeps ALB traffic encrypted from client to target.

An NLB TCP listener passes TLS through untouched when only the targets may decrypt traffic; ALB mTLS verify mode authenticates client certificates at the load balancer.

Deny statements with aws:SecureTransport false and s3:TlsVersion NumericLessThan 1.3 require HTTPS and TLS 1.3 for S3 access.

Databases need their own settings, such as rds.force_ssl for RDS for PostgreSQL and require_secure_transport for RDS for MySQL.

Last updated: September 2026

7.4 Enforcing Encryption in Transit: ELB Security Policies, TLS & HTTPS-Only Access

Skill 5.1.1 asks you to design mechanisms that require encryption when clients connect to resources, for example by configuring Elastic Load Balancing security policies and enforcing TLS. The exam cares less about TLS internals (general TLS concepts were removed from the outline) and more about where each AWS service lets you reject plaintext or weak connections.

  • Elastic Load Balancing
  • Application Load Balancer (ALB)

HTTPS listener with a certificate from ACM (or imported into ACM or IAM), plus an HTTP listener whose only action redirects to HTTPS (HTTP 301). The AWS Config managed rule alb-http-to-https-redirection-check detects ALBs that don't redirect.

Security policy : selects the TLS protocol versions and ciphers the listener accepts. When you create an HTTPS listener in the console, the default policy is ELBSecurityPolicy-TLS13-1-2-Res-PQ-2025-09 , which allows TLS 1.3 and TLS 1.2 with restricted ciphers and hybrid post-quantum key exchange. When you create a listener with the API or CLI without naming a policy, the default is the older ELBSecurityPolicy-2016-08 , so infrastructure-as-code templates should always set the policy explicitly.

Policy families : TLS 1.3-only policies, FIPS policies (for workloads that must use FIPS 140 validated cryptography), and post-quantum (PQ) policies. Choose the strictest policy your clients support.

Mutual TLS (mTLS) : In verify mode, the ALB authenticates client certificates against a trust store (CA bundle in S3, optional revocation lists). In passthrough mode, the ALB forwards the client certificate chain to targets in HTTP headers for the application to verify.

Re-encryption to targets : Use HTTPS target groups so traffic stays encrypted from the ALB to the targets. The ALB doesn't validate the target's certificate, so self-signed certificates on targets work, but the ALB can't detect an impersonating target.

Network Load Balancer (NLB)

A TLS listener terminates TLS on the NLB with an ACM certificate and a security policy, then re-encrypts to TLS targets or forwards in plaintext.

A TCP listener passes TLS through untouched when targets must terminate TLS themselves (for example, for end-to-end encryption or client-certificate authentication at the target).

Amazon CloudFront

  • Setting Recommended Value Effect
  • Viewer protocol policy Redirect HTTP to HTTPS, or HTTPS only Blocks or upgrades plaintext viewer requests

Viewer security policy (minimum protocol) TLSv1.2_2021 or newer Rejects clients using older TLS versions or weak ciphers

  • Origin protocol policy HTTPS only Encrypts traffic from edge to origin
  • Response headers policy Add Strict-Transport-Security (HSTS) Tells browsers to use HTTPS for future visits

The viewer certificate for a custom domain must be in ACM in us-east-1 .

Requiring TLS in Resource Policies

Many services accept both HTTP and HTTPS endpoints, or accept TLS 1.2 by default. Resource policies close the gap: {

  • "Sid": "DenyInsecureTransport",
  • "Effect": "Deny",
  • "Principal": "*",
  • "Action": "s3:*",
  • "Resource": [
  • "arn:aws:s3:::payments-data",
  • "arn:aws:s3:::payments-data/*"
  • ],
  • "Condition": { "Bool": { "aws:SecureTransport": "false" } }
  • }

aws:SecureTransport works in S3 bucket policies, SQS queue policies, SNS topic policies, and other resource policies. The Config rule s3-bucket-ssl-requests-only checks S3 buckets for it.

s3:TlsVersion is a numeric condition key; "NumericLessThan": { "s3:TlsVersion": "1.3" } in a deny statement requires TLS 1.3. AWS service endpoints already require at least TLS 1.2.

EFS file system policies can deny aws:SecureTransport false so that clients must mount with TLS ( mount -t efs -o tls ).

Enforcing TLS on Data Services

  • Service How to Require Encryption in Transit
  • Amazon RDS for PostgreSQL / SQL Server Set the rds.force_ssl parameter to 1
  • Amazon RDS for MySQL / MariaDB Set require_secure_transport to ON
  • Amazon Redshift Set the require_ssl parameter to true
  • Amazon ElastiCache Enable in-transit encryption on the cluster
  • Amazon OpenSearch Service Require HTTPS for all traffic and choose a TLS security policy (TLS 1.2 minimum)

Amazon API Gateway custom domains Select a TLS 1.2 (or stricter) security policy; enable mutual TLS with a trust store in S3 if clients must present certificates

  • Amazon SNS Use HTTPS subscriptions and deny aws:SecureTransport false in the topic policy
  • Detecting Gaps at Scale

AWS Config managed rules such as alb-http-to-https-redirection-check and s3-bucket-ssl-requests-only , deployed through a conformance pack, find non-compliant resources across accounts.

Security Hub CSPM controls report load balancers with HTTP listeners or outdated TLS policies.

AWS Firewall Manager can apply consistent AWS WAF and security group policies, and SCPs can deny CreateListener and ModifyListener calls unless the elasticloadbalancing:ListenerProtocol is HTTPS or TLS and the elasticloadbalancing:SecurityPolicy is an approved TLS 1.2 or 1.3 policy.

Specialty Exam Pitfalls

Relying on the API default policy : A listener created by script without a policy gets ELBSecurityPolicy-2016-08 ; specify a TLS 1.2 or 1.3 policy explicitly.

Assuming HTTPS to the ALB means HTTPS to targets : Configure HTTPS target groups when data must stay encrypted inside the VPC.

Terminating TLS where end-to-end encryption is required : Use an NLB TCP listener (TLS passthrough) if only the target may decrypt.

Forgetting non-HTTP services : Databases and caches need their own TLS settings; a secure load balancer doesn't protect database connections.

Loading diagram... Where Encryption in Transit Is Enforced